fix: iOS notification counts and sums are wacky #1796
Merged
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.
Description
Partial fix of #756, 2: (notification counts and sums)
This PR provides immediate relief for iOS users, specifically fixes iOS check to enable ek's fix (
initialValue = 1
) giving proper counting and sums on all notificationsos
value is not updated between events, this fix reliably saves and gets the OS value to/fromServiceWorkerStorage
Screenshots
AMOUNT counts
SUM_SATS sums
Additional Context
This is part of a series of fixes tracked on #1794
Checklist
Are your changes backwards compatible? Please answer below:
Yes
On a scale of 1-10 how well and how have you QA'd this change and any features it might affect? Please answer below:
9, didn't test
FOLLOW
but it follows (heh) the same counting method as others, tested also with withdraw/deposit sumsFor frontend changes: Tested on mobile, light and dark mode? Please answer below:
n/a
Did you introduce any new environment variables? If so, call them out explicitly here:
No