continuwuation/continuwuity

Fork 128

bug: Element X iOS: notifications silent (no sound/haptic) on 26.8.1 #2237

New issue

Closed

opened 2026-09-12 16:34:34 +00:00 by awiester · 8 comments

awiester commented

2026-09-12 16:34:34 +00:00

What is the bug?

Element X iOS, notifications come through as silent banners on 26.8.1, no sound or haptic

Steps to reproduce

Run Continuwuity 26.8.1 with an Element X iOS client, push rules set to Noisy
Bot sends a message to a room the iOS client is in (via HA notify.matrix_notify)
iPhone and watches get banner however, no sound, no haptic

Server name and version

26.8.1 (ab3c05d)

Additional context

I cherry-picked PR #1690 onto v0.5.8 back in May, later moved it to v0.5.9, ran it about five months, sound worked
I upgraded to 26.8.1 today, sound broke immediately
Nothing changed client-side: iPhone 16 Plus x2, Ultra 2 watch, Series 7 watch, same app, same push rules
- Push rules all Noisy in Element Web including bot and group chats, pusher registered, room unencrypted and local-only, still silent after full sign-out/sign-in, watches silent too
This is the iOS side of #914, which closed after Android got fixed in 25.09.0

### What is the bug? Element X iOS, notifications come through as silent banners on 26.8.1, no sound or haptic ### Steps to reproduce 1. Run Continuwuity 26.8.1 with an Element X iOS client, push rules set to Noisy 2. Bot sends a message to a room the iOS client is in (via HA notify.matrix_notify) 3. iPhone and watches get banner however, no sound, no haptic ### Server name and version 26.8.1 (ab3c05d) ### Additional context - I cherry-picked PR #1690 onto v0.5.8 back in May, later moved it to v0.5.9, ran it about five months, sound worked - I upgraded to 26.8.1 today, sound broke immediately - Nothing changed client-side: iPhone 16 Plus x2, Ultra 2 watch, Series 7 watch, same app, same push rules - Push rules all Noisy in Element Web including bot and group chats, pusher registered, room unencrypted and local-only, still silent after full sign-out/sign-in, watches silent too - This is the iOS side of [#914](https://forgejo.ellis.link/continuwuation/continuwuity/issues/914), which closed after Android got fixed in 25.09.0

awiester added the

Bug

Status

Needs Investigation

labels

2026-09-12 16:34:34 +00:00

nex commented

2026-09-12 16:35:39 +00:00

Owner

Duplicate of #1533?

awiester commented

2026-09-12 17:44:48 +00:00

Author

I have reslolved locally; notifications ring on 26.8.1 now, fix is based on #1690

The function collect_required_state in src/api/client/sync/v5.rs
The issue seems to be that $ME and $LAZY never get resolved, they fall through to a literal state lookup, nothing matches, so the power-levels event never reaches Element X and iOS notification still delivers as a banner, just without sound or haptic.
This appears to be the same cause as #1661, the function got rewritten but the fix was never added back.

Since #1690 was closed would the community welcome a PR for this?

I have reslolved locally; notifications ring on 26.8.1 now, fix is based on #1690 The function `collect_required_state` in `src/api/client/sync/v5.rs` The issue seems to be that $ME and $LAZY never get resolved, they fall through to a literal state lookup, nothing matches, so the power-levels event never reaches Element X and iOS notification still delivers as a banner, just without sound or haptic. This appears to be the same cause as #1661, the function got rewritten but the fix was never added back. Since #1690 was closed would the community welcome a PR for this?

nex commented

2026-09-12 17:47:51 +00:00

Owner

$ME and $LAZY don't exist, so probably not

`$ME` and `$LAZY` don't exist, so probably not

Henry-Hiles commented

2026-09-12 17:50:41 +00:00

Member

Yes, $ME and $LAZY aren't in the current SSS spec, Element X needs to fix their code to not depend upon them.

Henry-Hiles commented

2026-09-12 17:51:45 +00:00

Member

Closing as this is not a Continuwuity issue.

Henry-Hiles closed this issue

2026-09-12 17:51:45 +00:00

nex added

and removed

labels

2026-09-12 17:53:39 +00:00

Henry-Hiles commented

2026-09-12 17:56:07 +00:00

Member

No, we would not accept it. The fix should be in Element X, I'd recommend you contribute there if you wish to fix the issue.

👍 1

nex commented

2026-09-12 17:56:31 +00:00

Owner

People run custom patchsets all the time, so probably, but it's not something we'd accept as a contribution to the project. Feel free to make a fork and rebase it or something though!