[notifications][android] Add sticky
property to notifications
#9351
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
Implements changes proposed in #9302.
Current Notifications API provides
autoDismiss
property, which directly corresponds toautoCancel
on Android - it specifies if notification can be dismissed by tapping it, however it can be dismissed by swipe. Android API can also set notification asongoing
- it can be dismissed by tapping, but not by swiping.Expo legacy notification API had this property available, but it was replaced with
autoDismiss
in the new API.How
Added
sticky
property toNotificationContentInput
interface, used by local notifications. On native side - added it toNotificationContent.Builder
where needed and connected it with Android'ssetOngoing()
.Test Plan