feat(in_app_messaging): add custom Flutter display for campaigns - #18586
feat(in_app_messaging): add custom Flutter display for campaigns#18586SelaseKay wants to merge 3 commits into
Conversation
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. |
Wiz Scan Summary
To detect these findings earlier in the dev lifecycle, try the Wiz Code extension for VS Code, JetBrains, or Visual Studio. |
2af3e8e to
83fbb4d
Compare
83fbb4d to
6098684
Compare
2090354 to
edb1444
Compare
The example could not assemble on current Flutter (Gradle 8.14 / AGP 8.11). Export in-app messaging artifacts as api so app Java compilation can resolve FirebaseInAppMessagingDisplay.
Description
Adds an opt-in custom Flutter display path for In-App Messaging. Native SDKs already support replacing the default banner / modal / card / image-only templates; this wires that through to Dart.
setCustomDisplayEnabled(true)installs the plugin as the native display component. Listening toonMessageDisplayalone does not steal native UI.InAppMessage(title, body, images, colors, actions, campaign metadata, anddata). Apps draw their own widgets and reportimpress/click/dismiss/reportErrorso analytics and frequency capping keep working.messageDisplayComponentand reports callbacks through the executordisplayDelegate.FlutterApiand campaign/dismiss types from feat(in_app_messaging): expose the message lifecycle events #18584. This PR is stacked on that branch.Related Issues
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]).This will ensure a smooth and quick review process. Updating the
pubspec.yamland changelogs is not required.///).melos run analyze) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?