search

mollyim / mollyim-android

Enhanced and security-focused fork of Signal.
GNU Affero General Public License v3.0
1.37k stars 78 forks source link

Linked devices fail to register for FCM-based notifications #226

Closed chenxiaolong closed 8 months ago

chenxiaolong commented 8 months ago

Is there an existing issue for this?

Bug description

When using Molly as a linked device, FCM-based notifications don't seem to work despite Google Play Services being available. However, if it's set up as the primary device (same Molly version and build), then FCM-based notifications work.

Steps to reproduce

  1. Set up a primary device using either using Signal or Molly.
  2. Set up a linked device using Molly.
  3. Molly on the linked device immediately shows a an Optimize for missing Play Services message: Screenshot_20231013-001131

Force killing the app and starting it again doesn't seem to make a difference. The message disappears, but org.thoughtcrime.securesms.messages.IncomingMessageObserver$ForegroundService ultimately ends up running and seems to use the websocket method instead of FCM.

Molly version

v6.35.3-1

Android version

Android 14 and Android 13

Device

Google Pixel 7 Pro and Samsung Galaxy Tab S8 Ultra

Link to debug log

https://debuglogs.org/android/6.35.3/c8e739a1db336833b0977cf749592c0977e8de5111810dbd04135bc54229a7de

valldrac commented 8 months ago

Thanks for the detailed report. Unfortunately, the Signal server does not currently support FCM-based notifications on linked devices. It's limited to the primary device.

chenxiaolong commented 8 months ago

Ah, I wasn't aware of that. Thanks for the explanation!