microg / microg/GmsCore

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

Open
#1,935 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
14.6k
Forks
3.2k
Avg merge
12d 11h
Merged PRs (30d)
4

Description

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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, or code entry point is identified in the report. Start by reproducing the notification on Android 13 with microG, device registration, and cloud messaging enabled, then trace the communication-failure path. Done means the notification no longer appears during normal use and registration and push notifications continue working.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.