-
-
Notifications
You must be signed in to change notification settings - Fork 134
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
No username was found bug after updating username recently. #2190
Comments
This looks like your first issue on SkyCrypt! |
issue with an API we use for username revolving, cannot do anything here. temporary fix would be to use an UUID and then it should update an username |
Using a UUID does not update the username to the new one but it works as temporary fix, although it is a little bit annoying. |
yep, sadly we cannot do anything here. There's no other API that offers this kind of data without using multiple calls (which would slow down website even futher) |
does that mean it will update the username after a time? If so, do you know how long that would take, because It has been about a week |
Describe the bug
A "no username was found" error happens once entering new username. The new username has already been updated on api, because on other sites they work. SkyCryptError: No user with the name 'myusername' was found. This also happened to one of my friends and is annoying. You can only access it with the old username you previously had. Its actually also updating, me buying something also appears on skycrypt, however on the old username but not the new one.I have no idea if this is a known issue.
Profile/Location
On the site, for example my friend's username is Absorpy, however you can only access his skycrypt page via his old username (00122) the numbers are his username.
Expected behavior
Expect it to direct me to skycrypt page viewing profile information.
Desktop (please complete the following information):
Additional context
Most if not all context has been described
The text was updated successfully, but these errors were encountered: