"Something went wrong with your username, it's no longer assigned to your account"

[improvethings]

Using a supported version?

• I have searched searched open and closed issues for duplicates.
• I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

Overall summary

Signal Desktop 7.28 on osx

Steps to reproduce

1. Reopen Desktop 7.28
2. See error in the top left

Expected result

I don't expect to see that error and I don't want to change my username. It might be because I had username.number and it looks like the period is no longer accepted so needs to be namenumber now?

Actual result

Error warning persists when I open Desktop

Screenshots

Signal version

7.28

Operating system

osx

Version of Signal on your phone

7.18.2

Link to debug log

debug logs

[ayumi-signal]

Hi there, apologies this is happening to you. Was there any recent activity on Android like device transfer, or did the error just show up on desktop?

[improvethings]

Yes, sorry I should have mentioned this. A few weeks ago I bought a newer device (stock google) so I was going to move things over, starting with Signal (recovery from backup), but I decided yesterday to move it back (recovery from backup, overwriting the several week old instance still there) to the older non-google phone (GrapheneOS) before this error started.

[ayumi-signal]

I checked in with Android and learned it's related to the device transfer. We're looking into it. Sorry about that!

[LeeGDavis]

Hi, is there any kind of work around for this? I transferred an account to a new device as well and experiencing this. I also don't want to change my username.

[DidierLoiseau]

I’m also seeing this error today after transferring (back) to my newer phone last Wednesday. The error occurs on 2 different computers.

I also transferred back and forth between phones (to old one, RMA’ed the newer one in repair mode, then got it back and continued using it without reinstalling anything, just transferred Signal account back on it).

Note that I also had username issues with both Signal Desktop and Android after both transfers. In both cases I recovered my username (although with the old phone I had more issues as the app was initially crashing when trying to do that).

[scottnonnenberg-signal]

@DidierLoiseau I'm sorry about the difficulties you've had - can you provide the specific versions of Signal Android you used to do those transfers? We do believe that the issue is fixed at this point for that transfer scenario.

[tendstofortytwo]

Just had this issue with version 7.22.2 of the Android app, if that helps. It seems like this is the newest version on the Play Store atm.

edit: and 7.30.0 of the desktop client on Linux.

[scottnonnenberg-signal]

@tendstofortytwo Can we get debug logs from your Android device (Help/Debug log) and Desktop (View/Debug Log)? Also, what actions did you take - did you transfer from one Android device to another, like the others in this discussion?

[tendstofortytwo]

Phone log: https://debuglogs.org/android/7.22.2/e8e7c45bf5334d58d5c7e49e0c1179b793173b3b052f3f2e94d4560f2359af2a

Desktop log: https://debuglogs.org/desktop/7.30.0/a9363613c72c80ba1b877cb1886bd4c917e9051ae76e7650f23d4ae97671f3b6.gz

I restored from a backup after a factory reset of my phone.

[pepa65]

Transferred Signal to a new Android phone (now on 7.25.0), and Linux Desktop 7.34.0. The Desktop has the "something went wrong with your username" message. If I click "Fix now" it asks to Choose a username, when I choose my old one it pairs it with the correct number (as it is listed in the Android app: USERNAME.NUMBER). If I click Save, it says that recovering my username will reset my QR code and link. When I click Continue, it spins for a second and then is back to entering my username (already filled in). I can click Save to do this forever. If I click Cancel, I get back to what I had before...

[skeet70]

Android Version 7.25.2

I've been having this warning each day on my phone when I open the app. I follow the change flow, then get the same issue the next day.

This started after I linked a device that I'm using with the REST API via a container.