expo-notifications 57.0.22 → 58.1.6: deprecates 5 API(s)
Compared with 57.0.22: `getLastNotificationResponseAsync`, `clearLastNotificationResponseAsync`, `Subscription`, `NotificationBehavior.shouldShowAlert`, `NotificationCategoryOptions.allowAnnouncement`.
registry.npmjs.orgquote checked
- 58.1.6from 57.0.22
- Your code5 things to find
Nemotron fixes
In its own wordsread from the page
- getLastNotificationResponseAsync: Gets the notification response received most recently (a notification response designates an interaction with a notification, such as tapping on it). - `null` - if no notification response has been received yet - a [`NotificationResponse`](#notificationresponse) object - if a notification response was received Use `getLastNotificationResponse` instead.
- clearLastNotificationResponseAsync: Clears the notification response that was received most recently. May be used when an app selects a route based on the notification response, and it is undesirable to continue selecting the route after the response has already been handled. If a component is using the [`useLastNotificationResponse`](#uselastnotificationresponse) hook, this call will also clear the value returned by the hook. Use `clearLastNotificationResponse` instead.
- Subscription: use the [`EventSubscription`](#eventsubscription) type instead
What Teire looks for in your code
- getLastNotificationResponseAsync (ts)
- clearLastNotificationResponseAsync (ts)
- Subscription (ts)
- NotificationBehavior.shouldShowAlert (ts)
- NotificationCategoryOptions.allowAnnouncement (ts)
Does it reach your code?