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
In react-native, calling OneSignal.addTrigger does not display IAM under android 13. Sending test IAM in web dashboard works properly.
Steps to reproduce?
1. Use [email protected](com.onesignal:OneSignal:4.8.2)
1. Call `OneSignal.addTrigger` in react-native under android 13
What did you expect to happen?
Under android 13 device should diplay IAM.
com.onesignal.UserStateSynchronizer#doCreateOrNewSession calls https://api.onesignal.com/players and responses between android 12 and android 13 are different.
If above code is not executed, com.onesignal.OSInAppMessageController#messages has no message and com.onesignal.OSInAppMessageController#evaluateInAppMessages triggered by OneSignal.addTrigger in react-native does nothing.
If requset contains "device_os": "13" and "notification_types": 0, response have the in_app_messages attribute.
OneSignal Android SDK version
Release 4.8.2
Android version
12
Specific Android models
* Samsung SM-A325N
Relevant log output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
@zfanta Thanks for reporting with all these details. Just to confirm the issue, Android 13 works fine to display the Android 12 does not?
If that is the case that is expected, in Android 12 and lower notifications are enabled by default, there is no need to prompt them. This is why the you don't see the In-App Message in the in_app_messages payload.
The only exception to this is if manually turn off notifications at the operation system for your app this will work for any version of Android.
Closing issue due to no response. Please @ mention me if we need to revisit this issue.
We have an updated major release available for our Android SDK with many improvements and enhancements! Please refer to the migration guide for more information on upgrading.
What happened?
In react-native, calling
OneSignal.addTrigger
does not display IAM under android 13. Sending test IAM in web dashboard works properly.Steps to reproduce?
What did you expect to happen?
Under android 13 device should diplay IAM.
com.onesignal.UserStateSynchronizer#doCreateOrNewSession
callshttps://api.onesignal.com/players
and responses between android 12 and android 13 are different.Android 12 request
Android 12 response
Android 13 request
Android 13 response
Android 12 response does not have
in_app_messages
property, so this code is not executed.OneSignal-Android-SDK/OneSignalSDK/onesignal/src/main/java/com/onesignal/UserStateSynchronizer.java
Lines 445 to 446 in e119f4d
If above code is not executed,
com.onesignal.OSInAppMessageController#messages
has no message andcom.onesignal.OSInAppMessageController#evaluateInAppMessages
triggered byOneSignal.addTrigger
in react-native does nothing.If requset contains
"device_os": "13"
and"notification_types": 0
, response have thein_app_messages
attribute.OneSignal Android SDK version
Release 4.8.2
Android version
12
Specific Android models
* Samsung SM-A325N
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: