Signal "Unable To Connect To Service" Error after typing in SMS code

grapheneos-user-06

I have a very strange problem for which I have not been able to find a solution.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
tl;dr
after I get the SMS Code and typing it I get the Error Message "Unable to connect to service" or in original german: "Fehler beim Verbinden mit dem Dienst". If I try to get called by signal it shows me something like no connection, what can't be true because signal was able to initiate the SMS sending ...
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

maybe someone else had this nightmare and found a solution

Many posts on the internet are about not receiving the SMS code- also in this forum:
https://discuss.grapheneos.org/d/2899-signal-verification-issue

Or problems with their microG or other google services:
https://discuss.grapheneos.org/d/1256-signal-not-registering
https://discuss.grapheneos.org/d/807-signal-requiring-sandboxed-play-services

I'm really trying to pull myself together, because I can't believe that I have so much trouble with the most important app for me.
The number of registrations is also catastrophic because you have to enter a captcha every time and then a registration attempt is made, which is why you have to wait again immediately afterwards and after about 4 times you have to wait over 4 hours so that you can try again.

My first attempt at registration was like this:

fresh and up2date GrapheneOS
active Neguard VPN firewall (affect on signal completly disabled)
Gcam-Services-Provider for working google camera
signal installed from their official website
of corse no play services installed or other google stuff

I think I'm not so dumb, so after much research I tried to reduce the problem source as much as possible:

reset of grapheneOS
no active netguard VPN/"firewall"
no battery optimization
all permissions allowed
2x with my old phone number (1x without backup restoration, 1x with backup restoration)
2x with my new phone number (1x without backup restoration, 1x with backup restoration)
for the lulz I tried to register even a 3rd number of a family member who hasn't a smartphone

nothing works. I can't understand it.
I contacted the signal support but I can not believe they will really help me ... I send them the logs and hope they can analyze it.

Max-Zorin

Sounds like you had a similar issue with the number of attempts and blocking you out.

I attempted to obtain the SMS code through the app so many times (because Signal would not send it...) that Signal flagged my account as being suspicious. They didn't allow provide the option of a captcha and I had to wait "a period of time" which was not disclosed by the app, before I could try again. I tried 24 hours later and it worked,

The only thing I can suggest is to download the apk from the signal website https://signal.org/android/apk/ ,assuming you have not done so already, and see if that helps.

IMO Signal is going down the toilet.

grapheneos-user-06

Max-Zorin thanks for your comment! :)
As I wrote in my post, I already downloaded the current version of signal (Signal 6.13.6) and ... really, the FIRST try with my new number failed with exactly this message :|

Can't believe, I donated to the project. I'm not a dev, but I thought there is almost no phone that much ungoogled like a phone with grapheneOS ... and I have the feeling, that signal is contacting a google service for whatever reason.
I installed signal that way in the end of 2020 on my pixel 4 and until now never had almost any problems. That's really sad.

noxil

I have the exact same Problem. Fresh GraphenOS on Pixel6a and wanted to migrate from Pixel3a but got stuck in the verification loop you discribed. I tried different settings, but nothing work. Doing this for about 24 hours now. (Also wrote the support and send a screen cast for better understanding.)

grapheneos-user-06

I posted the question also on signal (Maybe I should have done that first :D)

https://community.signalusers.org/t/unable-to-connect-to-service-error-after-typing-in-sms-code-grapheneos/52184

A very nice user linked the github issue for this problem:

https://github.com/signalapp/Signal-Android/issues/12834#issuecomment-1464332467

Guess I'll have just to be patient until the updates will be also in the main version of signal :)

GrapheneOS

This is fixed by Signal 6.14.2 currently in their beta release stage. Would recommend just updating to it via Play Store beta or downloading from a mirror to update manually.

alex

6.13.7 has just been released via Play Store and direct download. This version should also contain the relevant fixes according to Cody. Can someone affected by the bug update and give it a shot?