element-hq
No notification or ring for an EC call
Steps to reproduce
- Remote user calls this phone using EC
Outcome
What did you expect?
Notification will get trigged and phone will ring
What happened instead?
Notification does not appear and phone does not ring
Push history shows,
Your phone model
Samsung S20 FE
Operating system version
Android 13
Application version and app store
Element X 25.05.3
Homeserver
Self hosted Synapse v1.129.0
Will you send logs?
Yes
Are you willing to provide a PR?
No
Multiple reports of this, here is the push notification error in text:
Unable to resolve event: msg=Unsupported Event Type,...
Stack backtrace:
0-3: <unknown>
4: uniffi_matrix_sdk_ffi_fn_method_timelineevent_event_type
5-7: <unkown>
- Idle: true
- Power Save Mode: false
- Ignoring Battery Opt...: true
- Device Light Idle Mode: false
- Low Power Standby Enabled: false
- Exempt from Low Power Standby: true
I have submitted more logs today from both the calling and receiving sides. What i noticed is that any calls made 'to' or 'from' this device triggers the same error message in the Push history.
@jmartinesp will this PR https://github.com/element-hq/element-x-android/pull/4722 fix this issue?
@jmartinesp will this PR #4722 fix this issue?
It just makes fetching notifications faster.
Looking at what I think are your logs, I think you're using the wrong call button: I only see logs for legacy call events that are no longer supported and were used by Jitsi, if I'm not mistaken.
uniffi.matrix_sdk.InternalException: Ignoring notification for call NotificationContent$MessageLike$CallAnswer uniffi.matrix_sdk.InternalException: Ignoring notification for call NotificationContent$MessageLike$CallCandidates uniffi.matrix_sdk.InternalException: Ignoring notification for call NotificationContent$MessageLike$CallHangup
In fact, I get the same on my device when I try to start a Jitsi call from Element Web.
Does the Element Web/Desktop UI look like this to you?
If it doesn't you need to enable Element Call in Settings -> Experiments -> New group call experience, then select the Element Call option you see in the screenshot.
The logs likely contain both EXA and legacy EA calls. I used the latter since EXA did not go through. However, I definitely did rage shake right after EXA failed to work. There definitely should be some of those in the submitted logs.
If you need more logs I can submit them too.
On Wed, 28 May, 2025, 13:18 Jorge Martin Espinosa, @.***> wrote:
jmartinesp left a comment (element-hq/element-x-android#4737) https://github.com/element-hq/element-x-android/issues/4737#issuecomment-2915322731
@jmartinesp https://github.com/jmartinesp will this PR #4722 https://github.com/element-hq/element-x-android/pull/4722 fix this issue?
It just makes fetching notifications faster.
Looking at what I think are your logs, I think you're using the wrong call button: I only see logs for legacy call events that are no longer supported and were used by Jitsi, if I'm not mistaken.
uniffi.matrix_sdk.InternalException: Ignoring notification for call NotificationContent$MessageLike$CallAnswer uniffi.matrix_sdk.InternalException: Ignoring notification for call NotificationContent$MessageLike$CallCandidates uniffi.matrix_sdk.InternalException: Ignoring notification for call NotificationContent$MessageLike$CallHangup
In fact, I get the same on my device when I try to start a Jitsi call from Element Web.
Does the Element Web/Desktop UI look like this to you? image.png (view on web) https://github.com/user-attachments/assets/c9b5dfd3-7454-423f-88ba-78131e34f27a
If it doesn't you need to enable Element Call in Settings -> Experiments -> New group call experience, then select the Element Call option you see in the screenshot.
— Reply to this email directly, view it on GitHub https://github.com/element-hq/element-x-android/issues/4737#issuecomment-2915322731, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAC4TAXFB23BG3CZE7WE7VT3AVS6TAVCNFSM6AAAAAB5KXWQ4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMJVGMZDENZTGE . You are receiving this because you authored the thread.Message ID: @.***>
Could you try upgrading to EXA 25.05.4? There is a possible fix for the 'Unsupported state event' issue.
Also, could you check for the event id of the m.call.notify event that failed to ring? I can't find anything in the logs about ringing calls, so I want to check if you didn't receive it at all or it was discarded for some reason.
@jmartinesp I upgraded to 25.05.4 via Google Playstore beta program. Submitted two logs marked as
- Sender EXA Github
#4737 - Receiver EXA Github
#4737
The receiver phone does not ring when a call is made by sender.