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

Clicking "Not seeing the prompt on your old device?" instantly crashes (iOS 18) #5881

Open
3 tasks done
lucaboesch opened this issue Sep 27, 2024 · 2 comments
Open
3 tasks done

Comments

@lucaboesch
Copy link

lucaboesch commented Sep 27, 2024

  • I have searched open and closed issues for duplicates
  • I am submitting a bug report for existing functionality that does not work as intended
  • This isn't a feature request or a discussion topic

Bug description

When trying to transfer to a new iPhone, the "Not seeing the prompt on your old device?" link does not work.

Steps to reproduce

  • have an old iPhone with a set up with a Signal account
  • have an new iPhone without a set up with a Signal account
  • Open Signal on the new iPhone
  • Try 'Transfer from iOS Device'.
  • The QR code (which BTW prompts 'THis QR code is not valid when scanned owith Signal on the old iPhone) appears.
  • Click 'Not seeing the prompt on your old device?'.

Actual result: The app crashes

Expected result: you get helped.

Screenshots

image

Device info

Device: iPhone 16

iOS version: 18

Signal version: 7.29

Link to debug log

@0xjmux
Copy link

0xjmux commented Sep 27, 2024

I had the same issue, but was able to solve it by making sure signal had the "Local Network Access" permission on both devices.

Hijacking this thread to suggest that (instead of crashing) the transfer flow should remind you that this permission is needed on BOTH devices, since right now the process is not very clear.

@lucaboesch
Copy link
Author

Thanks, @0xjmux !
Independentaly from your comment, when re-reading the requirements I did turn on local network access and then the process worked flawlessly.
Maybe this issue should be about amending the wording of the warning, then.

Best,
Luca

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

No branches or pull requests

2 participants