Open SahharWithu opened 1 week ago
Hi @SahharWithu,
When you create an in-app message subscription via the Dart code braze.subscribeToInAppMessages((BrazeInAppMessage inAppMessage) { }
, it will trigger the closure upon receiving an in-app message (not when clicking on it). The reason is that the in-app message UI is fully handled by the native iOS + Android layers by default, so we don't have a way to intercept the interactions in the Swift/Kotlin layer and port them via a subscription method into the Dart layer. However, through the native layer, we already log impressions, clicks, and button clicks by default.
If you would like to have full control of the IAM UI (appearance, metrics, etc), you would have to use the data models provided in subscribeToInAppMessages()
to create your own custom in the Dart layer. That way you can track clicks on your IAM and then determine what to do with that.
Hope this helps!
Which Platforms?
Both
Which Flutter Version?
3.22.2
Which Braze Flutter SDK version?
11.0.0
Repro Rate
100%
Steps To Reproduce
When subscribing to in-app messages using braze.subscribeToInAppMessages, I expect that the clickAction.uri should be received when an in-app message button is clicked. However, clickAction.uri is not being received on the Dart layer, despite setting up the correct logic for handling the click action.
Expected Behavior
clickAction.uri should be triggered and logged in the Dart layer when the in-app message button is clicked.
Actual Incorrect Behavior
Only ClickAction.none is triggered, and ClickAction.uri is not received.
Verbose Logs
i receive this log when i send test inapp message to ios18
Additional Information
Tested on ios 18 and Android 14 devices , both simulator and real devices , release and debug modes