"Finish linking on your other device"

[Hellmo-Luciferrari]

The problem

When trying to link via QR code from Signal on my mobile device, the QR Code is accepted; however when it is scanned I get a message telling me to "Finish linking on your other device"

Signal on Android version: 7.11.3

6c86af7a75c5 is the version for Signal-cli-rest-api

Are you using the latest released version?

• [X] Yes

Have you read the troubleshooting page?

• [X] Yes

What type of installation are you running?

signal-cli-rest-api Docker Container

In which mode are you using the docker container?

Native Mode

What's the architecture of your host system?

arm64

Additional information

Running via Docker Compose on a Pi 4 8gb

[bohart]

Got the same issue. Once QR code is scanned, the mobile app shows "Finish linking on your other device".

Additional details:

• an account details has been appeared at ./signal-cli-config/data/accounts.json
• but API request to /v1/accounts return nothing;
• API request to /v2/send return an error "User %mynumber% is not registered.";

[bobsiboo]

Got the same issue, When scanning the qr code a second time i just get a message Network error. I noticed there is an issue from last week with the same error. Maybe related?

[bbernhard]

unfortunately this is an upstream issue: https://github.com/AsamK/signal-cli/issues/1556

[ender-the-xenocide]

do you have any info as to why previous versions don't work then? I tried with 0.82 which uses signal-cli v 0.13.2 with the same issue. Where there backwards-incompatible changes on Signal's backend?

[xalik111]

have the same issue with latest version. any suggestions how can i fix it?

[k-bx]

As mentioned in https://github.com/AsamK/signal-cli/issues/1556 , this is fixed in latest master. In my case, I'm using signal-cli-rest-api and signal-cli-native without docker, so fixing is simple, just put the linked binary in your /usr/bin/signal-cli-native

[xalik111]

any chance if i use docker?

[Unpublished]

Upstream released the fix with v0.13.5

[bbernhard]

Please give this version a try: bbernhard/signal-cli-rest-api:0.164-dev

[ender-the-xenocide]

I confirm linking now works. thanks for the quick fix!

[ValentinFreelancer]

thank you sir

[HeyVern]

@bbernhard much appreciated! Looking forward to next release. Quick question for group. Do you think it would have been possible to use docker to remap the path in the container to an external folder and place the updated v013.5 binary there? I was considering trying this when I saw that a fix is incoming.

[ender-the-xenocide]

I imagine so - the last 2 commits are for taking the newer upstream lib, so in this particular case it might've worked. https://github.com/bbernhard/signal-cli-rest-api/commit/30615592b32bddec506868929aa21f45b9eafdda https://github.com/bbernhard/signal-cli-rest-api/commit/bb246cf3f7e786822a910194ba6f62cc2015e78c

[HeyVern]

Any ideas when we are going to se an updated release that includes this fix?

[ahatius]

Using the latest version (0.86, released yesterday) I was able to link my device again.

[pavacs]

A question for those who managed to connect their device. What needs to be done in hassio addons after the message Finish linking on your other device ?

[rzemykers]

at 0.88 in HA same issue.

[DBendit]

Seeing this with 0.86 and 0.88 today. No report upstream as far as I can tell.

[DBendit]

I was able to get past the issue by downloading https://github.com/AsamK/signal-cli/releases/tag/v0.13.6 and pointing it at the config dir and linking my device using the generated code.

[ge8020]

I am also stuck at "finish linking on your other device" with 0.88

[bbernhard]

Please give this version a try: bbernhard/signal-cli-rest-api:0.167-dev

[ge8020]

Please give this version a try: bbernhard/signal-cli-rest-api:0.167-dev

Thx, but sorry, i have no clue, how to try this?I´m not using the docker installation, but the home assistant add on from https://github.com/haberda/hassio_addons. And sorry, i just recognized that this is something different...

[thalesmaoa]

Please give this version a try: bbernhard/signal-cli-rest-api:0.167-dev

I confirm. It is working now.

[ge8020]

But how do you get this to work with the home assistant addon version?

[thalesmaoa]

@ge8020 , the main problem was that, latest version, it is not possible to add a new device. With the 0.167-dev that is working. Nothing changes after that.

[guschc]

Problem still existing with latest Home Assistant Add On that I installed today. After several "network error" messages, now stuck at "finish linking on other device" in the Signal app. Registering the number purely via API (instead of Signal App) did not work either: Getting around the captcha does not work, following the instructions eventually returns a "wrong captcha value" error message.

[p-roman]

Problem still existing with latest Home Assistant Add On that I installed today. After several "network error" messages, now stuck at "finish linking on other device" in the Signal app. Registering the number purely via API (instead of Signal App) did not work either: Getting around the captcha does not work, following the instructions eventually returns a "wrong captcha value" error message.

I know this is a closed issue, but I'm seeing the same thing with the Home Asssistant Add On, version 0.93.0. I was able to register it through the API, but I'd rather link it as a device...let me know if I should create a new issue instead. I tried enabling debugging logging, but don't think I can do that through the add-on version.

Edit: Nevermind, was able to set the debug level via the API and it turns out I had already tried registering the number, so once I got that cleared out, was able to link successfully.