[ANDROID] Notifications.getInitialNotification() no data when app is in kill state

[viktor-CCM]

Notifications.getInitialNotification() return undefined when the application is in a kill state.
If the application is foreground and the user tap on the notification - Notifications.events().registerNotificationOpened works properly.

const registerNotificationOpened = async () => {
    Notifications.events().registerNotificationOpened((notification) => {
      console.log('Notification opened by device user', notification.payload);
    });

    const initialNotification = await Notifications.getInitialNotification();
  };

Case 1 (Android)
Dead state (100% dead)
Click on the notification message
App will open
Notifications.getInitialNotification() return undefined

In iOS it works properly.

---

"react-native-notifications": "^4.3.1",
"react-native": "^0.69.6",

---

// Android Manifest

<uses-permission android:name="android.permission.INTERNET" />
<permission
        android:name="${applicationId}.permission.C2D_MESSAGE"
        android:protectionLevel="signature" />
<uses-permission android:name="${applicationId}.permission.C2D_MESSAGE" />
<uses-permission android:name="android.permission.VIBRATE" />
<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED"/>

<application
  android:name=".MainApplication"
  android:label="@string/app_name"
  android:icon="@mipmap/ic_launcher"
  android:roundIcon="@mipmap/ic_launcher_round"
  android:allowBackup="false"
  android:theme="@style/BootTheme">
    <meta-data
            android:name="com.google.firebase.messaging.default_notification_icon"
            android:resource="@drawable/notification_icon" />
    <!-- Set color used with incoming notification messages. This is used when no color is set for the incoming
                notification message. See README(https://goo.gl/6BKBk7) for more. -->
    <meta-data
            android:name="com.google.firebase.messaging.default_notification_color"
            android:resource="@color/primary" />
  <activity
    android:name=".MainActivity"
    android:label="@string/app_name"
    android:configChanges="keyboard|keyboardHidden|orientation|screenLayout|screenSize|smallestScreenSize|uiMode"
    android:launchMode="singleTask"
    android:windowSoftInputMode="adjustPan"
    android:exported="true">
    <intent-filter>
        <action android:name="android.intent.action.MAIN" />
        <category android:name="android.intent.category.LAUNCHER" />
    </intent-filter>
  </activity>
</application>

---

Google service package

dependencies {
    classpath("com.android.tools.build:gradle:7.1.1")
    classpath("com.facebook.react:react-native-gradle-plugin")
    classpath("de.undercouch:gradle-download-task:5.0.1")
    classpath 'com.google.gms:google-services:4.3.10'
    classpath 'com.google.firebase:firebase-crashlytics-gradle:2.9.2'
}

---

// Test devices
OnePlus 9R android 12
Pixel 4 API 30 (simulator)

[victorious85]

I faced the same issue

[Lapaenergy]

I have this problem too

[viktor-CCM]

I created a new project from template RN(npx react-native init AwesomeProject).
I used the guide from the documentation for the integration Android part.

I sent the following HTTP POST request to https://fcm.googleapis.com/fcm/send (via Postman). I got the push notification. But if app killed Notifications.getInitialNotification() return undefined.

[dmitrykurochka]

I have the same problem. Could someone help with it?

[viktor-CCM]

@DanielEliraz
I saw your first fix in PR. I checked it locally. It doesn't work.

[nschild]

I am seeing this same issue but also noticed that the initial props on my does carry android_notification_info. I am going to try tapping into that.

EDIT: Here is my working proof of concept

#push-notification-helper.ts

... {include all the stuff from the docs} 

export const loadInitialNotification = (initialNotification?: Notification) => {
    Notifications.getInitialNotification().then(async (notification = initialNotification) => {
        console.log(`getInitialNotification opened:`, notification);

        if (notification)
            onNotification(notification, AnalyticsLabel.Cold);
        else {
            store.dispatch(generalActionSetInitialNavigationState(undefined));
        }

        Notifications.events().registerNotificationOpened((notification2, completion) => {
            console.log(`Notification opened: `, notification2);
            onNotification(notification2, AnalyticsLabel.Warm);
            completion();
        });
    });
};

#App.tsx

export default class App extends Component {
  constructor(props: AppProps) {
    super(props);

    const notification = Platform.OS === 'android' && !!props.android_notification_info && ({
      identifier: props.android_notification_info.google?.message_id,
      payload: {data: props.android_notification_info},
      title: props.android_notification_info.title,
      body: props.android_notification_info.body,
      sound: '',
      badge: 1,
      type: '',
      thread: '',
    }) as Notification || undefined;

    loadInitialNotification(notification);
  }
  
  ...
 
}

[DanielEliraz]

@viktor-CCM do you expect that getInitialNotification will return the notification only when the application is in a kill state, while registerNotificationOpened will be triggered only when the application is in a background state?

[viktor-CCM]

@viktor-CCM do you expect that getInitialNotification will return the notification only when the application is in a kill state, while registerNotificationOpened will be triggered only when the application is in a background state?

@DanielEliraz Yes.

[DanielEliraz]

I think I found a way to trigger the registerNotificationOpened also in kill state. do you think it's an advantage or you prefer the way it is now?

@viktor-CCM do you expect that getInitialNotification will return the notification only when the application is in a kill state, while registerNotificationOpened will be triggered only when the application is in a background state?

@DanielEliraz Yes.

[viktor-CCM]

I think I found a way to trigger the registerNotificationOpened also in kill state. do you think it's an advantage or you prefer the way it is now?

@viktor-CCM do you expect that getInitialNotification will return the notification only when the application is in a kill state, while registerNotificationOpened will be triggered only when the application is in a background state?

@DanielEliraz Yes.

I like your way with registerNotificationOpened. But it will be breaking changes and it will be difficult migration (e.x different documentation for versions, migration guide).
All other libs use getInitialNotification, it is a common way.