Client doesn't send packets required to spawn
After joining a server, it's impossible to join a server. The client spawns, but it doesn't do that server-side.
I mean, it doesn't send the packets requeired to spawn. Tested that with another 0.6.0 iPod touch 4 as a server, and the iPhone refused to correctly connect (disconnected after 20 sec) until I manually closed Minecraft.
Also tested with PocketMine-MP, so I can tell you that the ReadyPacket (0x84) is not sent in that case. The first time after restarting Minecraft works.
Linked Issues
Created Issue:
Imposibility to correctly join a server after joining one.
After joining a server, it's impossible to join a server. The client spawns, but it doesn't do that server-side.
I mean, it doesn't send the packets requeired to spawn. Tested that with another 0.6.0 iPod touch 4 as a server, and the iPhone refused to correctly connect (disconnected after 20 sec) until I manually closed Minecraft.
Also tested with PocketMine-MP, so I can tell you that the ReadyPacket (0x84) is not sent in that case. The first time after restarting Minecraft works.
Imposibility to correctly join a server after joining one.Client doesn't send packets required to spawn
relates to
Could be related to MCPE-1216 .Check for the disconnect message
Related to MCPE-1216, try closing Minecraft from the multitasking bar
Related to MCPE-1216. Try closing Minecraft from the multitasking bar, then the multiplayer mode will work for a few times. Then, you'll have to do this again
It's related to MCPE-1216
The upcoming 0.6.1 release will fix this issue
Related to MCPE-1216
This has been already fixed, but Apple is still reviewing the 0.6.1 update
Shoghi, do you think this is the cause of issues like
MCPE-1233/MCPE-1252?Yes, sometimes the connection fails. Only tested on iOS, though, I'll test it now on Android
PD: Also, reinstalling Minecraft on the iPhone caused it to be more "stable", but the issue is still present
Also, the disconnect after 10 seconds it's caused by this, because the client/server have a timeout of 15-20 seconds
It's correct that client didn't send Ready-packet, but it was because it (on iOS) shut down the socket at a very unfortunate moment before Ready was dispatched.
Oh, thanks. At first, I though Mojang changed the protocol Handshake, but then tried restarting the App.
Looking for the update!