Cancel persistent notification when not using foreground service#300
Merged
tmo1 merged 1 commit intotmo1:masterfrom Sep 21, 2025
Merged
Cancel persistent notification when not using foreground service#300tmo1 merged 1 commit intotmo1:masterfrom
tmo1 merged 1 commit intotmo1:masterfrom
Conversation
chenxiaolong
force-pushed
the
cancel-notification
branch
from
d279404 to
4d9e858
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This was overlooked in 4eb8ebf where the non-foreground-service path is missing a mechanism for cancelling the persistent notification for the scheduled export status.
Fixes: #298