Skip to content

feat(in_app_messaging): add custom Flutter display for campaigns - #18586

Open
SelaseKay wants to merge 3 commits into
feat/iam-event-listenersfrom
feat/in-app-messaging-custom-display
Open

feat(in_app_messaging): add custom Flutter display for campaigns#18586
SelaseKay wants to merge 3 commits into
feat/iam-event-listenersfrom
feat/in-app-messaging-custom-display

Conversation

@SelaseKay

@SelaseKay SelaseKay commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

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 to onMessageDisplay alone does not steal native UI.
  • Eligible campaigns are forwarded as InAppMessage (title, body, images, colors, actions, campaign metadata, and data). Apps draw their own widgets and report impress / click / dismiss / reportError so analytics and frequency capping keep working.
  • The plugin does not open action URLs.
  • Android rebinds the display component on activity resume (the display SDK overwrites it) and restores the default templates when custom display is turned off. iOS sets messageDisplayComponent and reports callbacks through the executor displayDelegate.
  • Reuses the Pigeon FlutterApi and 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.yaml and changelogs is not required.

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
  • All existing and new tests are passing.
  • I updated/added relevant documentation (doc comments with ///).
  • The analyzer (melos run analyze) does not report any problems on my PR.
  • I read and followed the Flutter Style Guide.
  • I signed the CLA.
  • I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

  • Yes, this is a breaking change.
  • No, this is not a breaking change.

@gemini-code-assist

Copy link
Copy Markdown
Contributor
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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-9635d3485b

wiz-9635d3485b Bot commented Aug 20, 2026

Copy link
Copy Markdown

Wiz Scan Summary

Scanner Findings
Vulnerability Finding Vulnerabilities -
Data Finding Sensitive Data -
Secret Finding Secrets -
IaC Misconfiguration IaC Misconfigurations -
SAST Finding SAST Findings -
Software Management Finding Software Management Findings -
Total -

View scan details in Wiz

To detect these findings earlier in the dev lifecycle, try the Wiz Code extension for VS Code, JetBrains, or Visual Studio.

@SelaseKay
SelaseKay force-pushed the feat/in-app-messaging-custom-display branch from 2af3e8e to 83fbb4d Compare August 20, 2026 14:46
@SelaseKay
SelaseKay force-pushed the feat/in-app-messaging-custom-display branch from 83fbb4d to 6098684 Compare August 20, 2026 14:49
@SelaseKay
SelaseKay force-pushed the feat/in-app-messaging-custom-display branch from 2090354 to edb1444 Compare August 21, 2026 12:45
@SelaseKay
SelaseKay marked this pull request as ready for review August 21, 2026 13:53
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[firebase_in_app_messaging]: Support custom Flutter UI for In-App Messaging (expose native custom display component)

2 participants