You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some cases in which the native implementation does not have a current value for the unseen notifications badge (when it has not checked the current value yet or it has not been set by other means), the apps will send the response with no payload.
We need the GET_UNSEEN_NOTIFICATIONS_BADGE method to support responses without payload.
Also,the exported method: getUnseenNotificationsBadge: () => Promise<{unseenNotificationCounter: number; lastUpdated: number}>;
would need to change to something like: getUnseenNotificationsBadge: () => Promise<{unseenNotificationCounter: number; lastUpdated: number} | void>;
The text was updated successfully, but these errors were encountered:
kydorn
changed the title
Allow GET_UNSEEN_NOTIFICATIONS_BADGE empty payload
Allow GET_UNSEEN_NOTIFICATIONS_BADGE undefined payload
Nov 28, 2024
In some cases in which the native implementation does not have a current value for the unseen notifications badge (when it has not checked the current value yet or it has not been set by other means), the apps will send the response with no payload.
We need the GET_UNSEEN_NOTIFICATIONS_BADGE method to support responses without payload.
Also,the exported method:
getUnseenNotificationsBadge: () => Promise<{unseenNotificationCounter: number; lastUpdated: number}>;
would need to change to something like:
getUnseenNotificationsBadge: () => Promise<{unseenNotificationCounter: number; lastUpdated: number} | void>;
The text was updated successfully, but these errors were encountered: