Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App icon badge notification count is wrong. #3151

Open
ara4n opened this issue Aug 11, 2024 · 6 comments
Open

App icon badge notification count is wrong. #3151

ara4n opened this issue Aug 11, 2024 · 6 comments
Labels
A-Notifications O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect X-Needs-Backend

Comments

@ara4n
Copy link
Member

ara4n commented Aug 11, 2024

Steps to reproduce

The badge count on the icon is calculated by the server, not by the app, and so tends to be wrong.

Outcome

What did you expect?

Reliable app icon badge count

What happened instead?

We had #2066, but that was exacerbated by a synapse bug now fixed. The overall design problem from matrix-org/matrix-spec-proposals#4076 is still there though, and so the badge counts continue to be wrong...

Your phone model

No response

Operating system version

No response

Application version

675

Homeserver

No response

Will you send logs?

No

@Velin92 Velin92 added X-Needs-Backend S-Major Severely degrades major functionality or product features, with no satisfactory workaround O-Occasional Affects or can be seen by some users regularly or most users rarely A-Notifications and removed X-Maybe-Release-Blocker labels Aug 12, 2024
@itsthejb
Copy link

itsthejb commented Sep 2, 2024

I have suffered from this bug many times! I can accept that this is generally problematic, but going forward, is there any way to force reset the count from Synapse when this issue arises? Otherwise, could some reset cache button be added as an escape hatch as I believe resolves this is regular Element?

@pixlwave
Copy link
Member

pixlwave commented Sep 9, 2024

Otherwise, could some reset cache button be added as an escape hatch as I believe resolves this is regular Element?

This wouldn't help as the app would still be using the count from Synapse I'm afraid.

@itsthejb
Copy link

itsthejb commented Sep 9, 2024

@pixlwave But this is what I can't understand - I don't see this badge issue on any other client than Element X for iOS: even installing Element X on macOS results in the correct badge count. All regular Element clients also display it correctly. It's literally only Element X on my phone 🤷

@pixlwave
Copy link
Member

pixlwave commented Sep 9, 2024

Element iOS is using the badge number from Synapse until you open the app at which point it computes the badge locally as it has a copy of all the messages to use. Element X on the other hand is using Sliding Sync and with this, we don't (yet) have the code to fetch all of the necessary messages in order to do the computation locally.

@itsthejb
Copy link

itsthejb commented Sep 9, 2024

Ah I see. Ok thanks, that makes more sense

@ledlamp
Copy link

ledlamp commented Oct 3, 2024

This is super annoying and there seems to be nothing I can do besides disallow the badge. IMG_0806
IMG_0810

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Notifications O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect X-Needs-Backend
Projects
None yet
Development

No branches or pull requests

5 participants