Closed JordyLangen closed 2 years ago
Hi @JordyLangen,
Thanks for filing this issue! We have added this to our roadmap to update the implementation for the Automatic Android integration to accommodate use cases such as yours. In the meantime, you can use the workaround of setting com_braze_flutter_enable_automatic_integration_initializer
to false
in your Braze.xml
file and continue using the manual integration.
Best, Daniel
Just wondering, how is this an use case, and not a bug? I can't imagine anyone that would want to use the automatic integration and have an in app message both be shown nativly, and being handeld in their Flutter app.
@JordyLangen it works well for the default use case (automatic integration + native display) but as soon as a callback is added, it doesn't work anymore for the reasons you mentioned. It's effectively a bug and we should have an update to address it soon.
@Bucimis do you have any idea when this fix will be in? If it's anytime soon, we'd rather wait for that fix instead of keeping the "old" manual integration.
Hi @JordyLangen,
We don't have a timeline around this unfortunately, but we are aiming to add this change into our next Flutter release.
Thanks!
Hi @JordyLangen,
We have just released Flutter SDK version 2.3.0 which allows you to restrict the Android automatic integration from displaying in-app messages. You can read more about it in our public docs which have been added to the Braze website here.
Feel free to comment with any concerns - thank you for your patience!
Best, Daniel Hok
Steps to reproduce
Expected: The in app message is also handeld by the in app message handler
Actual: The in app message is shown using the Braze SDK itself and the in app message is also handeld by the in app message handler
Braze config:
I'm awaiting approval if I can share screenshots