-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Unable to transfer Signal account from my iPad to my new iPhone #5034
Comments
Just guessing here - could it be possible that you will need to enable camera access for Signal app in the configuration of the new iPhone? However, in that case I would expect corresponding explanation in the text of the error message. Anyway - maybe this helps... |
It looks like this is a duplicate of #4558 |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Signal needs to respond, it is still relevant. |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
@Stale this is still relevant |
Yes it is still relevant. Please reopen the issue. |
@Stale is causing way too much spam & confusion and even the original maintainers recommends against using it: probot/probot.github.io#376 |
Hi,
I had an iphone 11 pro max & an ipad pro 11in, both updated to the newest version of iOS.
I got a new iphone 12, and factory reset my iphone 11. However, I still have my full signal account running on my iPad pro 11in.
I'm trying to transfer my chat history from my signal account on my ipad pro to my new iphone 12.
However, when I try to make the transfer, I get an error message,
"To transfer your account, you must scan with your iPhone"
What do I do?
The text was updated successfully, but these errors were encountered: