[Android] Wire messenger does not notify about new messages, crashes when making call

[ellegance]

Please help, I have similar issues on several phones with Wire messenger app:

Motorola with Android 15, Google Services enabled. Wire app tested from both F-Droid and Google Play.
No notifications about incoming messages, when making call app just crashes. When Wire app opened I can see incoming messages but notifications don't work.
When pressed "Register FCM push token" Update button I get message:
Can't get notification error: DataNotFound
This behavior is on all versions of Wire, including latest 4.26.0-2494-fdroid
bf37b1e75
Only notification I receive is persistent notification on Wire start "Persistent WebSocket" "Wire is active"
I looked through all app settings, disabled any background restrictions but still no notifications and calls are not working.

I tested this app to ensure GCM is working well:
https://play.google.com/store/apps/details?id=com.alexbayker.firebasetester&hl=ru
pressed send Firebase message and immediately received notification.

Other messengers also works well.

I also tested with other phone without Google services and behavior is the same.

[MohamadJaara]

Hi thanks for the report one question when you installed the app and logged in did you have FCM working at that point on time or you enabled it after?

[ellegance]

@MohamadJaara yes, FCM was enabled on the phone before app installation

[MohamadJaara]

The F-Droid version of the app never ships with FCM support. If you need FCM-based push notifications, you would need to get the Play Store version of the app.
The F-Droid build uses a persistent WebSocket connection instead, which is why you see the "Persistent WebSocket" notification the app needs to stay active in the background to receive messages. This is by design for the F-Droid flavor, as FCM relies on proprietary Google Play Services.
Regarding the call crashes we recently fixed an issue that affected Huawei phones and impacted calling. You might be running into the same problem, so please try the latest version of the app and let us know if the crashes persist. if not please raise a support ticket so you will be able to share logs with us and take a look at the cause

[ellegance]

@MohamadJaara

When I updated app from F-Droid I can confirm outgoing calls now work, but still no new notifications about incoming messages.

When I changed it to Google Play version, Wire is stucked on "Wire setup: Please, wait, until we setup app for you" and circle running endlessly
Version 4.28.0-11961-prod
If look carefully, on app restart I see Wire logo animation, than on very short period of time I see app screen like main one, but then immediately "Wire setup: Please, wait, until we setup app for you" and circle running endlessly.

[MohamadJaara]

Sorry to hear this. I would love to investigate, but first I need some logs from the app.

1. shake the phone it open logs settings
2. enable logs and go back
3. restart the app and let it stuck for a little while to collect some logs
4. shake again and share logs with our customer support email, and I will take a look immediately.

NOTE: Please do not share logs publicly here.

[ellegance]

@MohamadJaara , well I am mostly interested in F-Droid version, at least it allows me to call and send/receive messages. The problem is notifications don't work. I shook phone, enabled logs, restarted wire several times, but wire_logs.txt file is empty 0 bytes

[MohamadJaara]

Small update from our side:

• The Google Play build getting stuck on “Wire setup” after login was identified and fixed.
• The empty wire_logs.txt / 0B logs issue is separate. We know what is causing it and will address it in a follow-up.
• For F-Droid, Wire does not use FCM. Message notifications depend on the Persistent WebSocket service.

Could you please check whether the “Persistent WebSocket / Wire is active” notification stays visible after starting Wire?

In particular:

• Does it remain visible after closing Wire or locking the phone?
• Or does it disappear after some time?

If that notification disappears, the background WebSocket service is likely no longer active, which would explain why new message notifications are only visible after opening the app again.