notifee.displayNotification(*) 'notification.id' invalid notification ID, expected a unique string value.

[edadma]

We're seeing

notifee.displayNotification(*) 'notification.id' invalid notification ID, expected a unique string value.

a lot on bugsnag. Has anyone seen this?

Here's the .displayNotification code:

          notificationListener = messaging().onMessage(async (notification) => {
            const channelId = await notifee.createChannel({
              id: 'default',
              name: 'Default Channel',
              importance: AndroidImportance.HIGH,
              description: 'Display notification while in foreground',
            })

            notifee.displayNotification({
              id: notification.messageId,
              title: notification.notification?.title,
              body: notification.notification?.body,
              data: notification.data,
              android: {
                sound: 'default',
                channelId: channelId,
                smallIcon: 'ic_stat_icon_push_notification',
                importance: AndroidImportance.HIGH,
              },
              ios: {
                sound: 'default',
              },
            })
          })

[mikehardy]

Yep, saw it when I did a basic search on repo

https://github.com/search?q=repo%3Ainvertase%2Fnotifee+invalid+notification+ID&type=code

notifee/packages/react-native/src/validators/validateNotification.ts

Lines 70 to 73 in ae2953b

	if (objectHasProperty(notification, 'id')) {
	if (!isString(notification.id) || !notification.id) {
	throw new Error("'notification.id' invalid notification ID, expected a unique string value.");
	}

Did you see that when you searched?

isString is doing a typeof

notifee/packages/react-native/src/utils/validate.ts

Lines 17 to 19 in ae2953b

	export function isString(value: any): value is string {
	return typeof value === 'string';
	}

Looks like either your code is sending in a null or something other than a string

What did you see when you console.log the notification information prior to calling the API function that isn't working for you?

[mikehardy]

(worth mentioning you do not include any version information so I'll just assume you are using current versions of...everything? But assumptions are dangerous when requesting or providing support, concrete information + full and complete issue reports always better)