This repository has been archived by the owner on Jun 20, 2023. It is now read-only.
Fix notification spam (EXPOSUREAPP-13503) #5330
Merged
Conversation
This file contains 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
SamuraiKek
added
bug
3 tasks
schauersbergern
approved these changes
Jul 7, 2022
|
Kudos, SonarCloud Quality Gate passed! |
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.
Spam was caused by wrong grouping of certificates where some users had slight name variations and had certificates that were eligible for booster. The previous grouping caused the
dccWalletInfoto always be null, triggering a recalculation of the wallet each time the app started or the background worker was performing it's task, subsequently triggering the booster notification over and over again.