When a person activates any resource pack that changes a player's animation, if it doesn't change the model, the animation usually breaks, or reverts to vanilla. I've tested it with 3 packs, all revert to Steve as the player skin, no matter what, meaning all skins appear as Steve, and only an old, slightly broken one that put in elbows and knees to the player didn't have the animations break in any way.
While resource packs in general causing bugs may not be supported in this, this is caused by any change to animation to the player in any way, not any specific pack.
Steps to reproduce
turn on a world, or go into one with a player animation changing resource pack
enter the world
view the player, arms paper doll, or 3rd person model
What is expected: the player's skin is preserved, and the animations do not break
What is observed: the player's skin, whether classic or made in the character creator reverts to steve, rarely with slightly glitchy textures.
If screenshots are wanted, I can take some and provide them.
Related issues
is duplicated by
Attachments
Comments


Could you attach a sample pack?


Additional info: it may be caused by optimization of keyframe animation playback, mentioned in the Official Minecraft Wiki in the version's bug fixes
Also, added pack that I used and noticed the bug with.

it also happens on servers like "Cubecraft" and "Hive"

Tested it again with the new update as usual, and despite it not being said on the full change log, the bug has been, very thankfully, fixed.

I don't think it's entirely fixed, it still applies to skins created with the Character Creator.
[media]
Capes also seem to still not work as well.

This bug also exists on Win 10.
Update:
Okay so I just deactivated the resource pack for the modified walking animations and I got my custom characters back. It's frankly not really a big loss in my opinion, as emotes now exist so.

Update: this seems to happen to character creator skins, while they may still show the intended animations and model that would be applied to steve, but classic skins now have the broken animations but don't revert to steve

Update: the previous beta from now had the broken animations on classic skins, and the character creator skins had working animations, but reverted to steve. Now character creator skins revert to steve, AND have the classic skin's broken animations. Plus, it seems that another animation changing resource pack, which also changed the player model simply crashes moments after the player loads.

Same happens with me on windows 10, for example I have a fully customised steve that defaults back to the default steve anytime I use a resource pack that affects the player. In my case it was a damage indicator resource pack.

Seems like at least on the public, non-beta version, at least one pack in the category now seems to crash the game when a world with the pack applied and nothing else, other than the mandatory base game packs, are applied. I'll add the pack mentioned.

Hello! When creating a Resource Pack, did you start making your resource pack by downloading it from the official Minecraft Addon Website? If so then the links to download is outdated. I have the same results. All custom characters are Steve's, the Steve texture is in the old texture, and capes are not appearing. Website is here: https://www.minecraft.net/en-us/addons

GlitchDestroyer, I actually got the addons from a website that has new addons and updates for the every day, and even has addons exclusive to it. I actually didn't ever download addons from the official website you mentioned, however.
Also, one of the resource packs listed, DetailedAnimations, is affected in a way that causes legs to now move in any way related to... anything except for jumping, causing some silly effects. After finding the creator doesn't mind if the code is reused, I attempted to find a possibility as to why the legs won't move, thinking that it had to do with there being no legs movement-related flag for walking, or sprinting, I added them, to any animations that would normally have the legs move. However, when starting up a world with the resource pack, I find what I did affected nothing.
The other animation resource pack, NPA, simply crashes every time I attempt to load a world with the pack applied.
Also occurs in the 1.16.220.50 beta, or rather the latest one as of this edit.

Also occurs in 1.17.0.50 beta

occurs in 1.17.0.52 beta.

It does, in fact, occur on the latest beta, as well.
Side note, on the bug tracker, for some reason new comments on the issues I report won't show, requiring me to look at my emails about the new changes/comments to see them.

this issue has never been fixed, it was and still is here on minecraft and its probably here to stay for a long time till the devs finally decide to fix it

This affects every pack that has player.json

For me the classic skins are not affected

still occurs in 1.18.10.20 beta

Affects 1.18

affects hotfix 1.18.12

affects preview/beta 1.18.20.29

Affects 1.18.30, 1.18.31, and 1.18.32. Aswell as all the 1.19 previews/betas.

Also, someone has probably mentioned this already but this bug also makes capes invisible.

Affects release 1.19

Something in my resource pack is causing this. Any tips on figuring out what it is so I can delete it?
Edit: Based on the earlier comment by wan6845 I removed two files from my resource pack, player.entity.json and player.render_controllers.json, and that fixed it.
Edit #2: Upon further playing I realized that although my skin now appeared, it was rendering completely black with RTX on. I restored player.render_controllers.json to its original location. That fixed everything. So in conclusion, I only deleted player.entity.json from my texture pack and that fixed it. Leave the other file I mentioned alone.

@Rogue Cheddar
I tried the same thing and it didn't work 😞
Were you just talking about classic skins, or were you able to restore your custom one made with the Character Creator?

I was able to restore my custom characters designed in the character creator. It probably depends on what texture pack you're using. I'm using a combination of Kelly's RTX, DefinedPBR, and a bunch of stuff I made. I would poke around and experiment with any files you have with "player" in the name

Affects 1.19.41

Someone please change the description. What actually triggers this bug is having a 'player.entity.json' file in the resource pack. Animations have nothing to do with this. Even if you download the sample resource pack from their official github, or extract the original files (via other methods) and try use an unmodified 'player.entity.json' file, the same bug will happen.

Affects 1.20.1

I'm on android, 1.20.10 and I had the described symptoms, where the character creator menu would not render anything but steve. premade skins were fine.
I tripped over this bug without realising the cause and tried a bunch of potentially destructive things like reinstalling the game. I was contemplating removing my skins to see if that resolved it, before i tested and realised my xbox wasn't having the issue.
I am using a health bar addon, so by removing player.json, i lose my health bars for other players, so i can't tell who needs help.

I dont know if anyone said this already but classic skins are not affected.
Examples of packs not affected: first birthday skin pack and literally any skin pack that can be imported by loading an .mcpack file.

Editing the player.entity.json in the resource pack disables persona usage in a world, this is still an issue in the 1.20.12 version of Minecraft.
What will happen the persona content will not render at all even when selected!

Affects 1.20.51

Affects 1.20.62

Affects 1.20.70/71 & 1.20.72

Same here, I added a Roblox jumping animation global packing and poof, Steve.

In 1.21, multiplayer server, capes won't display unless you are wearing an elytra, and standing near another player will change all players in the area to the same cape.

Guys i think i figured it out, I was looking though the "Vanilla Packs" resource pack on github, which states:
Minecraft: Bedrock Edition Vanilla Behavior pack and Resource pack files for the latest versions of Minecraft.
(Sourced from the template packs provided by Microsoft/Mojang.)
and I found this in the player.entity.json file:
"textures": {
"default": "textures/entity/steve",
"cape": "textures/entity/cape_invisible"
},
So I tested something out, I renamed the mcpack that had the issue into a .zip extracted and opened the player.entity.json file and just deleted that line of text and my cape was visible again! I remember having the Steve issue but that fixed itself somehow but if you are still having it I assume it's the same cause.
In short the sample texture pack that Microsoft/Mojang are providing have character set to Steve and capes disabled, most people when making packs probably use the official pack as a base instead of making one completely from scratch which made the issue wide spread.

@unknown It makes persona work because doing this breaks player.entity.json completely and the game just ignores it, so the result will be the same if you just remove that file from resource pack folder

Thank you for your report!
However, this issue has been closed as Working as Intended.
If you need help or have a suggestion you might like to follow a link below.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📓 Project Summary – 📧 Suggestions – 📖 Minecraft Wiki

@unknown Including that file in the resource pack literally breaks the whole persona service for no reason, can you please explain how is that intended?

How is it possible that this has been an issue for years and still hasn't been resolved? And now they come and mark it as "Works As Intended"? Seriously? They didn't even bother to check if it actually works! I just checked a moment ago, and it still doesn't work in 1.21.21

even having an empty "entity" folder in a Resource Pack brakes it
%localappdata%\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\resource_packs\Example_RP\entity
how is that "Working as Intended"?
I'm guessing they are trying to stop some kind of Dressing Room/ persona exploit.

Really not sure how this is WAI. How is it "intended" to have any player animations or animation-based UI changes break custom skins and capes entirely? Can this be reopened or the decision explained?

Really wish they would fix this, none of the packs I use work anymore and we are actively playing using packs. My friends are all Xbox users so they cannot download custom skins off the internet like I can and can only use Minecraft store skins now and it sucks! Especially since we were using our own original characters for roleplay purposes, but now they can no longer play as the skins they created for their characters in any of our worlds using packs, and most of our worlds do. This is especially troublesome for our horror worlds because they can no longer use custom horror character skins, meaning we cannot continue until it is fixed. 😞👎

This bug report is wrong. It is possible to safely change player.entity.json without breaking anything.
Use this file as a base instead of the file included with the vanilla resources:
[media]This fixed file is a combination of the 1.21.50 and vanilla player.entity.json files. Here are the steps to recreate it:
Download player.entity.json from the bedrock-samples GitHub
Add a "min_engine_version" of 1.8.0
Here is proof: a resource pack that changes player scale to 2.9375.
[media][media]
Thx you for telling us this information, @unknown! Can confirm that adding "min_engine_version": "1.8.0" to player.entity.json files on one of my affected resourcepack restores the cape and persona system 🙂

I need a further explanation on how to replace them. Like step to step.

It didn't worked for me, I need help.

The character creator ones are still Steve. You have to move the image
[media]
Just add
"min_engine_version": "1.8.0",
under the "identifier": "minecraft:player",

From the included media (check the earliest comment), the fix on “player.entity.json“ includes a variable:
"minimum_engine_version": 1.8.0,
on the header (after
"identifier": "minecraft:player",
, Thanks @Henry.Carm) of that file (Thanks @AgentMindStorm2), which solves the issue for the resource pack.
From @AgentMindStorm2 :
This bug report is wrong. It is possible to safely change player.entity.json without breaking anything.
…
Here are the steps to recreate it:
Download player.entity.json from the bedrock-samples GitHub
Add a "min_engine_version" of 1.8.0

For
"minimum_engine_version": 1.8.0,
I mean
"min_engine_version": 1.8.0,
and only that works, not "minimum_engine_version"
.