Signal-Android icon indicating copy to clipboard operation
Signal-Android copied to clipboard
verified publisher icon signalapp

Signal Not Registering With MicroG and uses WebSocket

Open Rafee-M opened this issue 1 year ago • 2 comments

  • [x] I have searched open and closed issues for duplicates
  • [x] I am submitting a bug report for existing functionality that does not work as intended
  • [x] I have read https://github.com/signalapp/Signal-Android/wiki/Submitting-useful-bug-reports
  • [x] This isn't a feature request or a discussion topic

Bug description

In microG settings, Signal isn't wouldn't recieve messages via microG/GCM anymore and would use websocket. It has been working fine before the recent update

Steps to reproduce

  • Unregister number from device and re-register
  • Go to microG settings > Cloud Messaging
  • Signal isn't there anymore

Actual result: Signal uses websocket and "Background Operations Enabled" notification is present Expected result: Signal app showing in microG and using gcm/fcm for messages. I have tried disabling the app and re-enabling it. Re-installing the same app and also turning microG cloud messaging on and off.

All my other apps work and I tried unregistering some of them and they re-registered automatically after turning registration on

Device info

Device: OnePlus 9 Android version: 13 Signal version: 7.5.2

Rafee-M avatar May 03 '24 17:05 Rafee-M

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] avatar Jul 03 '24 01:07 stale[bot]

I see exactly the same behaviour.

a52q microg 0.2.27.223616 signal 7.11.3 android 14 lineageos a52q-user 14 AP2A.240605.024 eng.root.20240701.003839 dev-keys

other apps register without problems

waldfee avatar Jul 18 '24 17:07 waldfee

I see exactly the same behaviour.

This got fixed for me after a Signal update and microG update. Not sure updating which one fixed it as previously updates from both sides didn't do anything.

Note: I am on microG's pre-release version 0.3.2.240913. But this issue was persistent for a while across multiple Signal and microG versions and while other apps were fine. Since it got fixed for me (not on microG stable tho), I'll be closing this. @waldfee since this an old issue maybe opening a new one might help

Rafee-M avatar Jul 25 '24 15:07 Rafee-M

I still have this issue on LineageOS 22.2-20250917-NIGHTLY-FP4, MicroG 0.3.7.250933, Signal 7.57.2. Same steps to reproduce, it's falling back to WebSockets

phoebehfharris avatar Oct 02 '25 18:10 phoebehfharris

Hey I moved to LOS as well. Try uninstalling Signal, reintstalling microG and install Signal again

Rafee-M avatar Oct 03 '25 11:10 Rafee-M