-
### What happened?
From one second to another (literally not doing anything, just stopping from building code, where it worked to building the archive where it didn't.) it stopped working. I get
…
-
### What happened?
In debug mode in android getting initWithContext error even without initialization
![Screenshot_20230912_123550_Cerebellum](https://github.com/OneSignal/react-native-onesignal/a…
-
### What happened?
I was able to build in Xcode 14, but after updating to version 15, I started getting errors.
![image](https://github.com/OneSignal/react-native-onesignal/assets/30148248/6dfc0f5…
-
### What happened?
We have identified a specific scenario where devices utilizing Firebase Social Authentication encounter an "APNS Bad Device Token" issue. Devices that have never utilized social …
-
### What happened?
The first time a page with our OneSignal implementation is loaded after clearing browser cache + cookies, the console shows a _409 Conflict_ error:
> OneSignalApiBase.js:67 PA…
-
### What happened?
If you open an application in Android in landscape orientation, push notifications come on top of the application; the addForegroundWillDisplayListener event does not work. Library…
-
I have generated a pwa app from a nuxt app and using oneSignal with web push sdk which has some restrictions (like automatically collapsing of older notifications when new notifications arrive) this …
-
In order to prevent duplicates, according to https://documentation.onesignal.com/docs/duplicated-notifications, you're supposed to set a notification ID when calling create().
I don't see this in t…
-
Hi, I am getting an error **Post https://onesignal.com/api/v1//notifications: http.DefaultTransport and http.DefaultClient are not available in App Engine**. Is there any way to solve this?
-
Push notifications are not working once we update our iphones to iOS version 13.
looks like some changes are required in order to support version 13.
https://onesignal.com/blog/ios-13-introduces-4…