Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
On Android, react-native-onesignal 3.2.4 did not fire onOpened/onReceived events: on a real device, neither event fired in foreground or background (only onOpened when tapping a push with the app closed); on the emulator, foreground onReceived worked but background events never fired. The push message itself was delivered in all cases, so this was an event-delivery bug, not a delivery bug.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
This was an SDK bug in the event handling. The OneSignal team fixed the underlying issue in 3.2.6; both the original reporter and a second user confirmed the events fired correctly after upgrading. Upgrade react-native-onesignal to 3.2.6 or later.
Source: https://github.com/OneSignal/react-native-onesignal/issues/583
Source: https://github.com/OneSignal/react-native-onesignal/issues/583
Shows how to fix react-native-onesignal: onOpened/onReceived events not firing on Android. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Shows how to fix react-native-onesignal 5.x: OneSignal.login(externalId) does not set external user id on Android. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Shows how to fix react-native-onesignal Android crash: Illegal callback invocation from native module. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.