[firebase_messaging]: FirebaseMessaging.instance.getInitialMessage() is always null on iOS after upgrade to 15.2.2

[lukyanov]

Is there an existing issue for this?

• I have searched the existing issues.

Which plugins are affected?

Messaging

Which platforms are affected?

iOS

Description

await FirebaseMessaging.instance.getInitialMessage() is always null when the app is opened from the "killed" state.

The plugin version 15.1.6 (the previous version I used) worked as expected.

iOS 18.3.1

@pragma('vm:entry-point')
Future<void> _firebaseMessagingBackgroundHandler(RemoteMessage message) async {
  await Firebase.initializeApp();
  RemoteMessage? initialMessage = await FirebaseMessaging.instance.getInitialMessage()
  // initialMessage is always null here
}

void main() async {
  FirebaseMessaging.onBackgroundMessage(_firebaseMessagingBackgroundHandler);
  ...
}

Reproducing the issue

1. Close the app (swipe it away)
2. Send a notification via firebase console or with a script (in my case I have a link attached to the notification data)
3. Tap the notification
4. Observe initialMessage being null

Firebase Core version

3.11.0

Flutter Version

3.27.2

Relevant Log Output

Flutter dependencies

No response

Additional context and comments

No response

[SelaseKay]

Hi @lukyanov, I've been able to reproduce this issue with the firebase_messaging example app. As a workaround, add a delay of 3 seconds before calling getInitialMessage and see if it resolves your issue.

[google-oss-bot]

Hey @lukyanov. We need more information to resolve this issue but there hasn't been an update in 7 weekdays. I'm marking the issue as stale and if there are no new updates in the next 7 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[austinwitherspoon]

A portion of users of my app on android have been hitting this issue suddenly over the past few weeks. Not sure if there was an android update that broke it, but for the affected users now every RemoteMessage ends up filled with null values.

[fahmisdk6]

I observe a similar issue on Android, will this issue be resolved?

[Kamuel09]

I’m not sure if this will be a hint, but when the RemoteMessage of getInitialMessage() is null, onMessage.listen does not work in the foreground state. However, when the RemoteMessage of getInitialMessage() is not null, onMessage.listen works in the foreground state.

The test was conducted on the Galaxy S25 Ultra, and normal operation was confirmed on the Galaxy Note 10 Plus and Galaxy S22.

[pranil-key]

facing same issue