-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linking device appears to silently fail #250
Comments
Same error on my side. I also use the AUR package |
I tried to fix it myself but didn't succeed yet. What I tried so far is adding
Maybe someone could point me in the right direction? |
Thank you for reporting. I will try to improve the error reporting and come back. |
Bump, same issue running gurk-bin 0.4.0-1, signal offical 6.39.1, also to note in signal app it says link successful, but it never shows up with a newly linked device, and if I spam trying to link it shows network error instead of link successful. |
If you link to often, they definitely rate limit you. JFYI: I am still looking into this issue. |
I'm also experiencing something similar. Using the latest release of gurk (0.4.1) and I can get the initial link to show up on my official signal client but when I close and open gurk then it tries to link again. |
I just tried to link with fresh installation. Basically, the application hangs on
Stopping it with CTRL-C and restarting, start an empty application which works though. |
Seems to work with the newest build! Although my sent messages are not synced from desktop to phone. Don't know if this has been an issue before. |
There was a bug which did not handle sync messages from other devices in groups. It was recently fixed here: #251. But there is another one, which is more subtle. My guess is that something is wrong with syncing prekeys. This is also what I am debugging right now. |
Currently failing to link with the latest build. |
Digging deeper. The provisioning stage succeeds in presage, but what fails is the confirmation stage
|
This commit upgrades presage to the latest available version. In particular, It includes the fix for the linking of secondary devices. For reference, the fix was done in: <whisperfish/presage#220> <whisperfish/presage#221> <whisperfish/libsignal-service-rs#271> Closes #250
This commit upgrades presage to the latest available version. In particular, It includes the fix for the linking of secondary devices. For reference, the fix was done in: <whisperfish/presage#220> <whisperfish/presage#221> <whisperfish/libsignal-service-rs#271> Closes #250
Hmmm, gurk-bin from AUR is still in v0.4.0, while thix fix was released in v0.4.2. |
Upon running
gurk
for a second time (and subsequent times after) the app simply creates a new QR code to use for linking the device. My guess is that it is failing the first time and afterwards, because under "linked devices" on Signal on my phone, the only link shown is the one I established with the official app. No error is being shown, even when using the--verbose
argument, so I assume it's silently failing and trying again when I try to run it again.On the off chance it's relevant, I'm using the
gurk-bin
package from the AUR, version 0.4.0-1. The device I'm using to link it via QR code is running version 6.37.2 of the official Signal app on Android.The text was updated successfully, but these errors were encountered: