Skip to content

feat(in_app_messaging): expose the message lifecycle events - #18584

Open
Lyokone wants to merge 1 commit into
mainfrom
feat/iam-event-listeners
Open

feat(in_app_messaging): expose the message lifecycle events#18584
Lyokone wants to merge 1 commit into
mainfrom
feat/iam-event-listeners

Conversation

@Lyokone

@Lyokone Lyokone commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Description

  • Adds the message lifecycle to FirebaseInAppMessaging as onMessageClicked, onMessageImpression, onMessageDismissed and onMessageDisplayError, carrying the campaign metadata and, for clicks, the action URL and button text. A new Pigeon FlutterApi forwards the events, Android registers its four listeners on a main thread executor, and iOS conforms to InAppMessagingDisplayDelegate. Two platform differences are documented rather than emulated: Android reports no dismiss type, so InAppMessagingDismissType.unknown is used there, and onMessageDisplayError reports the Android InAppMessagingErrorReason name on Android and the localized error description on iOS.
  • Attaches the native listeners the first time one of the streams is read rather than at plugin registration. On iOS InAppMessaging.delegate is a single slot, so attaching eagerly would take it from apps that set it in native code; apps that never use these streams keep the current behavior.

Related Issues

Checklist

  • 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

  • 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.

Adds `onMessageClicked`, `onMessageImpression`, `onMessageDismissed` and
`onMessageDisplayError` to `FirebaseInAppMessaging`, so apps can react to
what happens to a campaign message - most importantly read the action URL
of the button a user tapped, together with the campaign metadata.

The native listeners are attached the first time one of the streams is
read, so apps that never listen keep the current behavior and, on iOS,
keep ownership of the `InAppMessaging` display delegate.

Android reports no dismiss type, so `InAppMessagingDismissType.unknown`
is always used there.

Closes #12984
@SelaseKay
SelaseKay force-pushed the feat/iam-event-listeners branch from 5d73bd8 to 3487ae3 Compare August 21, 2026 12:45
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.

馃悰 [in_app_messaging] Add suport for event listener for Card interactions

3 participants