Skip to content
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

addDevice not accepting "device link" #1562

Closed
2 of 3 tasks
ilippert opened this issue Aug 4, 2024 · 1 comment · Fixed by #1561
Closed
2 of 3 tasks

addDevice not accepting "device link" #1562

ilippert opened this issue Aug 4, 2024 · 1 comment · Fixed by #1561

Comments

@ilippert
Copy link
Contributor

ilippert commented Aug 4, 2024

The problem: addDevice does not lead to expected result

Chatter: Thanks so much for signal-cli!

This is how the problem (repeatedly) appears, some things work, some don't:

  • registering the phone number,
  • sending and receiving messages
  • addDevice
signal-cli -u +49XXXXX addDevice --uri 'sgnl://linkdevice?uuid=....&pub_key=....'

generates as a result

ERROR AddDeviceCommand - Invalid device link
Invalid device link

I tried the sgnl://linkdevice?uuid=....&pub_key=.... identifiers multiple times (restart a linux Signal Desktop app, scanning the QR code, pasting in the shell within the '...').

I suspect that --uri 'sgnl://linkdevice?uuid=....&pub_key=....' has to include the &pub_key=.... component, but am not actually sure. If it is correct, then #1561 may be helping others to be certain they are pasting the correct string.

I guess following #139 that % should not be an issue.

I am grateful for questions that help me revise this issue so that it becomes legible and productive.

@ilippert
Copy link
Contributor Author

ilippert commented Aug 4, 2024

Found the solution, it was the problem, that I extracted &amp from the QR code and used that instead of the required &.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant