search

microg / GmsCore

Free implementation of Play Services
https://microg.org
Apache License 2.0
8.2k stars 1.69k forks source link

[org.thoughtcrime.securesms] Signal shows a "Permanent Signal communication failure!" notification #1935

Open GamerTechUni opened 1 year ago

GamerTechUni commented 1 year ago

Affected app Name: Signal Package id: org.thoughtcrime.securesms

Describe the bug When using Signal with microg with device registration and cloud messaging enabled, an error will pop up after a few hours of use of the phone. The error is a notification that appears, which says "Permanent Signal communication failure!" Even though microg settings shows that the app is registered, when you click on the notification, it says that "Signal won't run without Google Play services, which are not supported by your device." When I tried push notifications on Discord, the notifications just worked. I also disabled adaway just to be sure, but it still happens.

To Reproduce Steps to reproduce the behavior:

  1. Open Signal
  2. Register or log in with device registration and cloud messaging enabled in microg
  3. Wait for a few hours
  4. Communication error shows up

Expected behavior No errors should pop up and everything should work fine.

Screenshots https://imgur.com/a/nGL4Ibg

System Android Version: 13 Custom ROM: LineageOS 20

microG microG Core version: 0.2.27.223616 microG Self-Check results: All ticked

Additional context Magisk and microg installed (using magisk), also fakegapps is installed using lsposed

j0110 commented 1 year ago

Try to update the app, or the reinstall it. It could solve the problem

foolishgrunt commented 3 weeks ago

Well, seeing that this issue is still open, I guess I'll tag on here rather then create a new one.

On my Pixel 3a, I recently upgraded from LimeageOS for microG v20 to LineageOS (vanilla) v21. Dirty flash, no factory reset or anything. Before the upgrade, on LOS for microG, everything worked fine - out of the box if I recall correctly. But after upgrading to vanilla LOS, I get the same errors reported above, i.e. this notification: Screenshot_20240816-130144_RetroArch_1 When I hit the notification, it opens Signal and displays this message: Screenshot_20240816-121637_Signal_1 I have GmsCore (microG Services) and GsfProxy (microG Services Framework) installed, and every self check box is checked except fakestore: Screenshot_20240821-215018_microG Services

The notification shows up every few hours. I do get push notifications of new messages arriving, but occasionally (frequently enough to be a problem) do not receive them unless I have the Signal app open.

In case anybody suspects the dirty flash, in this house I also transitioned a Pixel 6a from Google Android to LOS 21 at the same time, and it has identical issues.

ale5000-git commented 3 weeks ago

@foolishgrunt Your error is pretty clear, after the change you still have microG Services, but you lost microG Companion (Phonesky in the screenshot). Just install it again.

foolishgrunt commented 3 weeks ago

I see, stupid me. I saw the commit message about microG Companion moving into the same repository as GmsCore, and thought it said that Companion was being merged into the same package. Thanks for straightening me out.

I've installed it now, no "Regsitration failure" notification so far.

ale5000-git commented 3 weeks ago

They were merged in the same repo because some of the source code is now shared between them but they are still separate apps.