-
Notifications
You must be signed in to change notification settings - Fork 199
After hosted browser update, usernames don't come through (only IDs) #1758
Comments
Note this is not just on the hosted browser. It's on the local browser as well. No user is going to know that they need to deny an auth request, refresh on the browser home page, double-check their ids, then go log in. This is already breaking experiences for users and people are reporting it across apps. |
Yeah, we have some code to 'refresh identities', which picks up the username from your addresses. We only have it on a few places, like the 'view more IDs' page. We need to add this to onboarding, and a few other pages that people might run into this issue. |
Cool. This one is especially bad because every user is required to update the browser when there is an update. There's no opt-out for the hosted browser. |
@hstove not following your comment. We've pushed maybe 5-10 updates in the past year and this is the first time I remember this reported. Think this is a new bug in the latest build. @jehunter5811 you agree? |
That’s correct. This specific issue has never happened before as far as I can remember. |
I can confirm that this is also an issue that seems to affect multiple different things. My social links got deleted, as did my username, profile bio, and my profile picture which is now unable to be updated. Some apps, like Graphite, I have to switch around which browsers I use, while others just flat out fail entirely. (GitHub, for whatever reason, won't allow me to upload a screenshot to show what I mean. I would if I could.) |
@SouthernWolf95 Have you found that your social links, etc. get restored as expected upon reauthentication? |
The latest release should fix this issue. |
Verified this fix. Thanks @yknl |
After updating the browser, usernames are not populated. The user would have to stop the auth flow, go to the IDs page, refresh, then go back to the app and log in again to have their username come through after a browser update.
The text was updated successfully, but these errors were encountered: