this issue occurred for me through synchronization between the Android and Nintendo switch versions of the game using the same account.
on the Nintendo switch I have platform-restricted skins, which understandably can't be used on Android.
the game however does attempt to sync this skin, resulting in an error on the Android version every time the character selection screen is opened.
imported skins on Android cannot be synchronized to the Nintendo switch either and cause loading problems as well, but this causes issues that are more unpredictable.
I've had the skin/character appear as invisible or as Alex in the character select screen on the Nintendo switch, and after returning to android this character would either be restored to the imported skin, be replaced with Steve, or be deleted altogether.
I think a solution would be to prevent the downloading(and overwriting) of incompatible characters/skins, and keeping "last used skin" synchronization locked to the platform.
or alternatively separate skin-pack skins and imported skins from the new custom character system, and simply don't synchronize the "active" skin/character if an imported or skin-pack skin is in use.
Linked issues
is duplicated by 1
Comments 9
behavior has changed for the better, but is still not ideal.
going from console to mobile:
mobile always shows an error that the skin in the slot with the platform locked cannot be loaded, now showing a "reload" icon on this slot.
if the slot with the platform restricted skin was the last one used a default skin is loaded, but this doesn't overwrite the slot.(good, although it would be preferable if instead it would use the last skin used on mobile)
going from mobile to console:
no error is shown.
a slot with an unsupported skin simply reverts to a default skin but this isn't synchronized back, so unless you edit the skin in this slot the slot will still have the custom skin on mobile.
so skin customizations are no longer outright deleted when switching between platforms, what remains is just minor inconveniences.
suggestions for improvements on this:
mark slots with platform specific skins as "unavailable on this platform" without an error sound.
don't sync which skin slot was last used, instead always start with the slot last used on that platform.
I wonder if this is related to the newly discovered MCPE-106662, since they both have something to do with platform restricted content and cross-platform play
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response
Is this still an issue in the latest version? If so, please make sure the ticket description contains the following information:
Steps to Reproduce:
1.
2.
3.Observed Results:
(Briefly describe what happens)Expected Results:
(Briefly describe what should happen)
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Going back through old reports. This had been fixed in an earlier beta release but has not made it into a public release yet (as of 1.17.32). The fix is still present in the latest beta, so a fix may come in 1.17.40.
while not ideal, the biggest part of the issue is resolved.
platform-specific skins show up as steve or alex on unsupported platforms, and when returning to the platform supported by the skin(unless edited on the unsupported platform) the steve/alex skin will turn back into the platform specific skin again.
having some way of separating out platform-specific skins would be nice, but at least the behaviour is consistent and non-destructive.
Affects 1.16.40
In some cases, syncing platform restricted skins can result in unexpected behavior, such as deleted or reset character creator skins and/or skins displaying "failed to load character" errors, these effects can even affect the original device where the skins were added. If there is no way to fix this, there should at least be an explanation for why this happens.
Above information added from MCPE-103270