Couldn't look up profile properties issue

[sanegaming]

Describe the bug

The server is constantly spamming the console chat with various player profiles with the following error:

[17:56:20 WARN]: Couldn't look up profile properties for com.mojang.authlib.GameProfile@6a736d2e[id=00000000-0000-0000-0009-01fd43ae45cf,name=.E1ectroxity,properties={},legacy=false]
java.lang.IllegalArgumentException: Name and ID cannot both be blank
at com.mojang.authlib.GameProfile.(GameProfile.java:26) ~[authlib-3.5.41.jar:?]
at com.mojang.authlib.yggdrasil.YggdrasilMinecraftSessionService.fillGameProfile(YggdrasilMinecraftSessionService.java:203) ~[authlib-3.5.41.jar:?]
at com.destroystokyo.paper.profile.PaperMinecraftSessionService.fillGameProfile(PaperMinecraftSessionService.java:38) ~[paper-1.19.jar:git-Paper-42]
at com.mojang.authlib.yggdrasil.YggdrasilMinecraftSessionService.fillProfileProperties(YggdrasilMinecraftSessionService.java:175) ~[authlib-3.5.41.jar:?]
at com.destroystokyo.paper.profile.PaperMinecraftSessionService.fillProfileProperties(PaperMinecraftSessionService.java:31) ~[paper-1.19.jar:git-Paper-42]
at net.minecraft.world.level.block.entity.SkullBlockEntity.lambda$updateGameprofile$3(SkullBlockEntity.java:142) ~[?:?]
at net.minecraft.Util.ifElse(Util.java:460) ~[?:?]
at net.minecraft.world.level.block.entity.SkullBlockEntity.lambda$updateGameprofile$6(SkullBlockEntity.java:139) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
at java.lang.Thread.run(Thread.java:833) ~[?:?]

To Reproduce

Unsure, this server was upgraded from 1.18 to 1.19 and has had this issue since 1.19

Expected behaviour

I would expect if the profile is invalid to delete it, or automatically add the Name/ID as it is requesting.

Screenshots / Videos

No response

Server Version and Plugins

No response

Geyser Dump

https://dump.geysermc.org/rhFyiwjFn7s16YFjKlbs97t4NKiytdMf

Geyser Version

2.0.4-SNAPSHOT (git-master-f2f894b)

Minecraft: Bedrock Edition Device/Version

All devices

Additional Context

No response

[Camotoy]

This has to do with looking up player heads. It's safe to ignore, and is technically a Floodgate issue.

[ijgeoffrey]

Nice to know that this is safe to ignore, but it's definitely very annoying as a server admin because I get about 20 of them and it buries the other data in my server console.

[sanegaming]

This has to do with looking up player heads. It's safe to ignore, and is technically a Floodgate issue.

Isn't this the floodgate github?

[Konicai]

Yes. This is the right place - its a Floodgate issue

[hedrizzle]

Still open the Issue on 1.20.2 Purpur: https://pastebin.com/XVpaxQRB
Geyser-Dumb: https://dump.geysermc.org/isTMAE7FJQbRaM3P207VL91dphN6UOh0

[hedrizzle]

@sanegaming @Camotoy @ijgeoffrey @Konicai

I just found the solution!

i bet you guys are all on Windows Server, right?
Exlude in Windows Defender your minecraft server folder and no error in logs anymore! you're welcome xD

[Konicai]

The specific error you had isn't related to this issue

Please avoid pinging everyone in a conversation

[hedrizzle]

hm, ok, maybe not but the solution for me is still working with excluding it from windows defender. maybe someone will help this comment.
sorry for pinging everyone, it was my first post ever on github.

[MatinHQ]

Still no solution for that?

[Tim203]

Is this still a problem?

[ServerNootNoot]

Yes, this is still a problem.

[Tim203]

Which server version are you using?

[ServerNootNoot]

I'm using 1.20.4.

[TerdyTheTerd]

I see these issues on 1.21.1 Purpur with Geyser/Floodgate. Extremely annoying when the console gets hundreds of lines spammed in an instant multiple times over the course of a few minutes. Whatever "feature" is triggering these needs to have an option to disabled it.

[Tim203]

Player heads cause this. Some see this as a Floodgate issue because the Java server doesn't expect the Floodgate UUIDs, but I personally see it as improper error handling of the server.
The only thing you can disable is Floodgate itself, then the issue doesn't silently disappear though because the player heads of Floodgate players continue to exist in your world.

[Camotoy]

On further evaluation, this might be something we can work around. Please provide a Geyser dump.

[TerdyTheTerd]

Well that's the thing, one of the UUID's is a Java UUID, it was saved somewhere in the server when I joined the backend server while it was in offline mode. It only fails with ONE of the bedrock UUID's and not both, likely because I had also joined with that bedrock account while it was in offline mode.

In any case, what is triggering these? Is it only player heads of those players?