-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
"Something went wrong with your QR code and username link, it's no longer valid" #6883
Comments
Hello, sorry this is happening for you. Can you please send us debug logs? (View Menu -> Debug Log) |
2 debugs, And Ill try to catch one when the error re-appears. |
@alternativesurfer Thanks for this. Looks like this is the Android log. Could you share the Desktop log as well? |
Thank you! We will look into it. |
same issue here using MacOS (log after pressing fix): |
@Theoreticallyhugo did you a link a new desktop/iPad recently? Could you submit a log from your phone, please? Sorry about the issue! |
@indutny-signal I'm using signal-cli but linked it not long before getting myself a QR/ username. Thank you for your help :D |
sad news, celebrated too early... |
Still occurring for me. |
@alternativesurfer Is it the same thing as your original report? You see the warning, you fix it, and then a few hours it comes back? Can you tell us more about your primary Signal device (phone) and all of your linked devices? If we could get a fresh log from each of those, we should be able to track this down. Thanks! |
Same as my original report, yes. Pixel 8 Linked devices: logs |
I'm having this issue too. If I try to fix my username (it forces me to pick a different one, which I don't want to do) and that still doesn't work anyway... |
@asanghc can you provide debug logs from your desktop and android device? |
The same is happening to me right now, on desktop, after transferring signal from my old to my new phone.
Here are my signal on desktop logs (windows 10): https://debuglogs.org/desktop/7.17.0/25b2e61b961af1cf679d022c89206152713343eacc32205df65095b96093fd01.gz |
Exactly the same as @lucidBrot . Just transferred to new Samsung phone and re-linked my desktop app and seemed fine. Then noticed there was a signal update on desktop, installed that and presto Username bug.... |
@basharoot sorry about this; could you share debug logs from your desktop & phone? |
Sure thing! Thanks for putting eyeballs on this. Desktop Client: Android App: |
Same issue here, just tried switching from one Android to another using the transfer feature (didn't work) and after transferring manually got the "Something went wrong with your username, it's no longer assigned to your account. You can try and set it again or choosea new one." message. Signal 7.15.4 |
Same issue here. Just switched to a new Android device and re-linked my two laptops. Both say "Something went wrong with your username". No indication of a problem on my new Android device. Desktop client: Android app: |
Same here. New s24, transfered the account and this error occurs. |
Same issue here, account moved from a Pixel 8 to a Pixel 9 Pro... this was done by backing up, activating on new phone and restoring the backup. The desktop app was the first to nag, and I'd totally wiped the data and uninstalled on the desktop thinking that this was a linked device issue and a bad data state... but now the Pixel 9 Pro device itself is showing the message. When I reset the QR code on the device, with the desktop disconnected fully, it resolves it for a short while and then the message returns (on both the mobile device and the desktop app... though not instantly on both, a few days pass and then the message appears on one of the apps and when I check the message is also on the other). I'm on stock Android but came from GrapheneOS, unsure that this makes a difference. |
Adding logs since I'm running into this too. Transferred from Pixel 8 Pro to Pixel 9 Pro Fold using the app. No errors displayed for at least a week, then I noticed the error yesterday in the app. I show no linked devices, but I previously had it connected to Linux Mint desktop. I haven't accessed the desktop app in a very long time, maybe a year. |
Clicked on fix now and the error has gone away. I'll update here if it returns. |
Hello everyone! We believe the issue should be fixed in Signal Android 7.17.2 . Please make sure that both devices run the version above 7.17.2 before doing the transfer to avoid the username/link issues. Thank you for reports! |
How do we fix being in this state for those that were operating on latest
prior to this fix?
…On Mon, Sep 23, 2024 at 1:07 PM Fedor Indutny ***@***.***> wrote:
Hello everyone! We believe the issue should be fixed in Signal Android
7.17.2 . Please make sure that both devices run the version above 7.17.2
before doing the transfer to avoid the username/link issues. Thank you for
reports!
—
Reply to this email directly, view it on GitHub
<#6883 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACZZ7KBYNYBZJHBKKMC4C5DZYA4FLAVCNFSM6AAAAABIB4N4EWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRYG42DAMZWGA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
@calvin940 Great question! If you were on Android >= 7.17.2 when you encountered the issue - please provide debug logs from both Android (most importantly) and Desktop. |
Apologies as I may have not been clear. When I performed this (about a
month and a half ago), this fix wasn't in place so I am still having that
fix username message. I was asking how do we (people in this current state)
fix this issue without having to change our username.
…On Mon, Sep 23, 2024 at 2:14 PM Fedor Indutny ***@***.***> wrote:
@calvin940 <https://github.com/calvin940> Great question! If you were on
Android >= 7.17.2 when you encountered the issue - please provide debug
logs from both Android (most importantly) and Desktop.
—
Reply to this email directly, view it on GitHub
<#6883 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACZZ7KGTRLECTGSVO2I6LV3ZYBD6LAVCNFSM6AAAAABIB4N4EWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRYHA4DSMRXGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Ah, I see. I think clicking the "Fix" button in the UI is the best way forward. You should be able to select the desired username (which could be the same as before) from there! Let me know if it doesn't work! |
I'm still having this issue. iPhone, iPad, and MacOS. https://debuglogs.org/ios/7.29.0/19e82700d1ce68031f2b787eb41ecd8886b29040d2c47264702904f08da65939.zip |
@JoshuaACNewman this sounds like an iPhone bug. Could you report it to https://github.com/signalapp/Signal-iOS/issues/new?assignees=&labels=&projects=&template=bug_report.md&title= and include iPhone logs as well? Thank you! |
Using a supported version?
Overall summary
I have this error on my Signal Desktop
If I click "Fix Now" it goes away for a few hours but then returns.
I have duplicated this on a few different installs with different registered #'s/Usernames
Steps to reproduce
Expected result
No error about the QR code/Username link
Actual result
An error about the QR code/Username link
Screenshots
Signal version
7.9.0
Operating system
Windows 11 Enterprise
Version of Signal on your phone
7.6.2 and 7.7.1
Link to debug log
No response
The text was updated successfully, but these errors were encountered: