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
InAppMessage display when redisplay after 5 minutes
Current Behavior
inAppMessage don't show when go to backgond 5 minutes or more.
Possible Solution
I check issue related if set dismiss is false
Steps to Reproduce
open app and show inAppMessage
go to backgroud and waiting for 5 minutes
go to forground again
I don't see inAppMessage show anymore
SDK Version
core: 2+
inappmessaging: 2+
Android Version
Build Environment
Android Studio Flamingo Version 2022.2.1 patch 1
Gradle Version 7.2
Android Gradle Plugin Version 7.2.0
Context Details
Logs
Possible Implementation
None
The text was updated successfully, but these errors were encountered:
LocLt-Mobile
changed the title
[Android] inAppMessage not show when go to background 5 minutes or more
[inAppMessage] action popup not show when go to background 5 minutes or more
Nov 29, 2023
LocLt-Mobile
changed the title
[inAppMessage] action popup not show when go to background 5 minutes or more
[inAppMessage] action popup don't show when go to background 5 minutes or more
Nov 29, 2023
LocLt-Mobile
changed the title
[inAppMessage] action popup don't show when go to background 5 minutes or more
[inAppMessage] action popup don't show when go to background after 5 minutes or more
Nov 30, 2023
This is was a bug with JS SDK referenced within Android SDK.
Fixed version was released on February 5.
The latest version of the JS SDK is always referenced, so there is no need to update the Android SDK.
Please check it out.
Expected Behavior
InAppMessage display when redisplay after 5 minutes
Current Behavior
inAppMessage don't show when go to backgond 5 minutes or more.
Possible Solution
I check issue related if set dismiss is false
Steps to Reproduce
SDK Version
Android Version
Build Environment
Context Details
Logs
Possible Implementation
None
The text was updated successfully, but these errors were encountered: