-
Notifications
You must be signed in to change notification settings - Fork 373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[iOS] When app is in background "opened" callback does not fire #613
Comments
I have the same issue, but it happens on Android. When the app is in background mode, the user taps on an incoming notification, the opened callback is not firing and there is no additionalData in received callback. I test it in Android simulator 8.0.0 and physical device 8.1.0. Any one has the same issue even in Android or IOS ? Environment |
Yeah I can confirm I can see this occasionally on android as well.
…--
Regards
Steve Robinson
On 30-Aug-2018, at 3:58 PM, motogod ***@***.***> wrote:
I have the same issue, but it is happens on Android.
When the app is in background mode, and the user taps on an incoming notification, the opened callback is not firing and the there is no additionalData in received callback.
I test it in Android simulator 8.0.0 and physical device 8.1.0.
Any one has the same issue even in Android or IOS ?
Environment
"react": "16.3.1",
"react-native": "~0.55.2",
"react-native-onesignal": "^3.2.6"
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@steverob Apologies for the delayed response, can you reproduce this issue in our example project? If so - can you please upload it to dropbox and post a link? The example project is in the |
Closing due to no response - if you're still running into this problem please feel free to respond and I'll be happy to reopen and help investigate |
@steverob since I cannot reproduce this issue, can you attempt to reproduce it in our demo project? 90% of the time when a user reports this problem it usually turns out to be user error, so it would be good to make sure you can reproduce it in our demo project. If you can, it would be very helpful to share a Dropbox link |
It still happens, especially on iOS background service. |
Description:
When the app is in background mode, and the user taps on an incoming notification, the
opened
callback is not firing.When the app is in focus, and we have
OneSignal.inFocusDisplaying(2)
set, the notification shows and if the user taps it, nothing happens.received
callback is fired though.On Android, in both cases when I tap the notification, the
opened
callback is firing without any issues.Is this the expected behaviour? What I want to happen is - when the notification is displayed (app is in background) and the user taps it, the app should be opened and the
opened
callback should be fired so that I can navigate the user to a screen (using a deeplink sent withadditionalData
).Environment
OneSignal RN SDK -
3.2.6
RN -
0.55.4
iOS -
11.2.6
AppDelegate.m - https://gist.github.com/steverob/25c969ded98dce44ca168309d67a103f
I followed the setup instructions detailed in the documentation and also added the
Notification Service Extension
.The text was updated successfully, but these errors were encountered: