Only returns "old" profile data?

[CobbleShop]

trafficstars

Just tested the API and it returns the old (or first?) name of an user. Not the current. Will this be solved?

[zanethefox]

I've also encountered this issue for multiple weeks now unfortunately. Would it please be possible for you @Electroid to take a quick look when you have a moment?

For example this UUID returns an old username when fetched via the Ashcon API: https://api.ashcon.app/mojang/v2/user/e5eca375dfd2499a9f7aa387b906e7d8

And when using the Mojang API it shows the correct updated one: https://sessionserver.mojang.com/session/minecraft/profile/e5eca375dfd2499a9f7aa387b906e7d8

Thanks a lot for your time and work :)

[zanethefox]

Hey @Electroid have you had a chance to take a look into this? Unfortuantely the API is still returning outdated profile information. Thanks :D

[CobbleShop]

I don't think he's still actively working on this 👎

[zanethefox]

@CobbleShop Yeah :( It seems like it.

I can imagine it might just be a caching issue with the worker or something.

[Electroid]

I haven't had the time recently to look into this, will try to this weekend.

[zanethefox]

Really appreciate it, thank you! 😊

[kyngs]

Hi, I want to confirm that this issue still appears.

It's apparent for example on this player, who changed their nickname, here's the ashcon data and official data: https://api.ashcon.app/mojang/v2/user/gonza_001 https://api.mojang.com/users/profiles/minecraft/gonza_001

We can also see, that ashcon reports incorrect data for their new nickname: https://api.ashcon.app/mojang/v2/user/DroppedByGonza01 We can see that the returned username does not match the queried one.

[kyngs]

It seems like playerdb.co exhibits the same behavior, kinda a weird coincidence

[kyngs]

I haven't had the time recently to look into this, will try to this weekend.

Hey, can you look into it in the near future?

[zanethefox]

Hi there @Electroid sorry for the ping but did you get a chance to look into this yet? Thanks a lot :)