This repository was archived by the owner on Jan 14, 2025. It is now read-only.
Fix example app cancel notification #869
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The `lastId` should reflect the last id used not the next id to be used. When the lastId is set to the next id to be used the `cancelNotif` function will try to cancel a id not yet used.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When testing the example app, I found it unable to cancel the last notification.
This issue was caused by the
lastIdvariable representing the next id to be used instead of the id of the last created notification.Because of that the
cancelNotiffunction would try to cancel a notification not yet created.To test this change:
Schedule a notification in 30sCancel last notification (if any)