You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using Android app, use this lib and add a custom urlHandler which processes the url and returns true
Open the Android device, and then hit home button to place app in background (but still running)
Using Iterable Web UI, send a test push from a template with a Push open action of Open URL
On Android device, press the push
Expected
App will process the push url, and come into focus
Actual
App will process push url fully in background, but not come into focus
Environment:
@iterable/react-native-sdk1.0.12
react-native0.63.1
Android OS10
Suspected cause
Looking at this code, it seems the Android SDK is designed to not focus the app if the event is handled. This may be fine for an Android SDK, but this RN SDK doesn't have a way to bring the app into focus if it reports the url is handled.
Current workaround
For Android only, we return false in our urlHandler, basically disabling our custom url handler, and we make sure to use urls to double as valid deep links. This works for now, but is a somewhat limited solution.
The text was updated successfully, but these errors were encountered:
After further integration work, we found that this was also the case whenever customActionHandler was set, and unlike with the urlHandler we could not do a simple workaround.
We dived into the code and submitted #79 which should clear the issue, and result in consistent behavior between iOS/Android when pressing on push notifications.
We're thankful these libraries are own source, allowing us to speed forward to fix our implementation while providing feedback on what we found.
Reproduction
urlHandler
which processes theurl
and returnstrue
home
button to place app in background (but still running)Push open action
ofOpen URL
Expected
Actual
Environment:
@iterable/react-native-sdk
1.0.12
react-native
0.63.1
Android OS
10
Suspected cause
Looking at this code, it seems the Android SDK is designed to not focus the app if the event is handled. This may be fine for an Android SDK, but this RN SDK doesn't have a way to bring the app into focus if it reports the url is handled.
Current workaround
For Android only, we return
false
in oururlHandler
, basically disabling our custom url handler, and we make sure to useurls
to double as valid deep links. This works for now, but is a somewhat limited solution.The text was updated successfully, but these errors were encountered: