We expected the skins menu to always show the player in a neutral standing pose. When the player was in a different pose (sitting in a minecart or a boat, crouching or sneaking, for example) when most previously quitting out of the world, then some of the skins menu models will show player models having that last pose instead of having a neutral standing pose. This seems to affect single and multiplayer, creative and survival.
To Reproduce
Original report
When riding a boat and left the game and check the SKIN PACK turned BOAT ANIMATION. Bush 10.0 MyTablet
To Reproduce
Go to a world and ride a boat
Leave the game
Go option and look at the Skin packs
The Skin packs Skin turn Boat Animation
Attachments
Comments 17

I can reproduce it. You must be in survival mode and have to open the inventory and go in the armor tab before closing the world.
Confirmed on Asus Zenfone 5 Android 5.0
I can reproduce it. You must be in survival mode and have to open the inventory and go in the armor tab before closing the world.
Confirmed on Asus Zenfone 5 Android 5.0
All you need to reproduce this bug is to have the player render sitting when you leave the game Wether it be in the armor tab or 3rd person view. This happens to all skins in the skin selection with the same model as the player's skin. So if the player is using the skinny arm model all skins with skin arms will sit, same with fat arms.
All you need to reproduce this bug is to have the player render sitting when you leave the game Wether it be in the armor tab or 3rd person view. This happens to all skins in the skin selection with the same model as the player's skin. So if the player is using the skinny arm model all skins with skin arms will sit, same with fat arms.
Can't reproduce on Samsung Galaxy S6 (SM-G920W8), Android 5.1.1, MCPE 0.13.1 with any of the skin packs. I'll try my Win 10 tablet later and if I still cannot reproduce, I'll resolve as fixed in 0.13.1.
Can't reproduce on Samsung Galaxy S6 (SM-G920W8), Android 5.1.1, MCPE 0.13.1 with any of the skin packs. I'll try my Win 10 tablet later and if I still cannot reproduce, I'll resolve as fixed in 0.13.1.
I am afraid we can not reproduce this bug in the recent version. Please update affected versions if this bug still occurs.