Problem Summary:
I am completely unable to upload or apply custom skins to Minecraft Bedrock Edition on my Android device, despite the skins being valid and functioning perfectly on my Windows 10 Bedrock Edition.
Custom .png skins (64 x 64) were created using SkinSeed
Skin worked flawlessly on PC (same account), but didn’t sync to Mobile device
Attempts to import skin manually on android results in this error: “Please import a .png file of dimensions 64 x 64” even though the file is 64 x 64
What I Have Tried:
Reinstalled Minecraft
Cleared cache and storage
Tried .png files made from SkinSeed, exported raw, and cleaned through photoshop
Used “import > choose new skin” from dressing room
Attempted to sync through Microsoft account (signed in on both pc and mobile)
Used trusted skin apps to apply the skin directly - resulted in default skin or sync error
Tried .mcpack and .mcaddon installations (both failed to load or are ignored)
Attempted file manager methods with ZArchiver and MT Manager
Verified file structure under “/Andriod/data/com.mojang.minecraftpe/… “ - denied write permissions even with advanced apps
Created custom characters in Character Creator (on pc) - but they do not appear on phone
Results:
All skin import methods fail.
Even when a skin appears to import, I’m stuck with a default Steve skin.
This have been consistent for multiple reinstallations and across multiple app versions. There is clearly either a bug in skin syncing, or a file permissions issue where the app is unable to access its own directories properly.
Additional Notes:
The same .png works when uploaded from PC
Microsoft cloud syncing does not propagate the skin to mobile
Multiple tools (Skindex, NovaSkin, MCpack, ect.) do not work on mobile
This seems to be a Minecraft/Android permission + skin system bug that blocks skin imports and ignores syncing characters
Below, I’ve attached The error message, the skin that was attempted to be uploaded, and “proof” of the image size being 64 x 64.
Thank you.
Related issues
Attachments
Comments


This issue is being tracked at MCPE-170910.