search

johanw666 / Signal-Android

Fork from a private messenger for Android with extra options added: full backup and (partial, ony text) xml backup of messages. Restore can happen at any time, not only after a fresh install. Import SMS database. Import of (unencrypted) WhatsApp databases. Removed apk expire. Choose between passphrase protection and the Android screenlock. Choice for the backup location (internal or removable storage on Android < 11 (on 11 and higher this is already possible)). Set the maptype in the place picker. Option to treat view-once media as normal media. Option to ignore remote deletion. Choose between FCM or websocket notification delivery.
https://johanw.home.xs4all.nl/Signal/signal-jw.html
GNU Affero General Public License v3.0
246 stars 16 forks source link

Deregistered Account with App Update #100

Closed arthurghwindsor closed 2 months ago

arthurghwindsor commented 2 months ago

Whenever updates are made by installing on top of a previous version it "de-registers" the account from Signal's servers. The person with the JW app after update can still send messages like normal and the receiver can still receive the messages however the chat window would say the number is not registered with signal. Attached is a screenshot of the error on my fiance's phone using Molly when chatting with me (I use the JW version) Screenshot_20240511-125757~2

johanw666 commented 2 months ago

Odd. I had issues with registrations years ago but those were solved years ago and were not related to updates. Can you send a debug log?

arthurghwindsor commented 2 months ago

After updating I cleared the App storage to reactivate my account so I've successfully recreated the error by downloading the previous version (7.7.0.0-JW) and updating it to the latest version (7.7.1.0-JW) and I'm sending the debug files for both versions (named accordingly). Btw this has been happening for some time now and I just thought Signal was trying to block access from forks so I didn't think much of it until I noticed the pattern after every update. (7.7.0.0-JW)signal-log-1715527929075.zip (7.7.1.0-JW)signal-log-1715529390867.zip

johanw666 commented 2 months ago

Pixel with grapheneOS and using websockets. And I see lines like FcmRefreshJob: FCM reregistration failed after retry attempt exhaustion! in the log.

I assume this is nothing specific from my fork but Signal being too strict (again) when they deregister an account server-side. The symptoms sound the same as those I had, the issue then turned out I had no Googe account active on the device but did use gms for notifications. I suggest this is moved to the main Signal repo because there isn't much I can do server side.

As a temporary solution I used to switch manualy to websockets (that is why this option is in my fork at all), you can try it and see if it helps: Settings - Privacy - Advanced - push notifications via fcm. The app will restart after you change that option.

arthurghwindsor commented 2 months ago

Thanks it solved the issue, also using Google FCM on GrapheneOS barely manages to deliver notifications on time anyway so...