Samaritan

Was able to reproduce this with default Mesa Drivers on Ubuntu in both 1.17.1 and the latest snapshot (21w43a), attached relevant screenshots.
Didn't affect 1.16.5, didn't seem to affect Windows 10 when I checked on the latest snapshot .

similar to MC-168230

Everything said here is based off my limited understanding for this component.

There aren't many examples of mob behaviors being changed by updates that I know of. (I suspect that it is no longer enabled by default, as I noticed that old spawns of the hostile Phantom seemed to attack despite being from the update where they didn't. Though it is also possible that the Phantom has the component disabled already). Any issues caused by this component would be temporary, once the mob(s) in question despawn or are killed, no mobs will have the issue. But now knowing that such a component exists, I don't know why it should or would be enabled for vanilla mobs in vanilla worlds. I can't check for sure to see if this component is still enabled by default, I just know that it was at some time for a handful of mobs.

Hypothetical (this is assuming that the component is still set this way, and is set this way for all vanilla mobs);
The behavior of a tamable mob gets changed. Say it has some new ability. When players would go to try the new ability they would find out that they are unable to because their version of the mob spawned before the update that added the ability.
Or say there's a bug involving an invincible hostile mob. The old spawns of the mobs would remain invincible after the bug fix.

A past example was where there was an issue that caused Magma Cubes to take fall damage from their own jumps. After the bug had been fixed, any Magma Cubes created before the fix were still taking fall damage. (Though the problem lasted for about 10 seconds thanks to their own jumps eventually killing them, thus this example quickly resolved itself in a somewhat morbid way).

The component doesn't cause any problems until something relating to mob behavior is changed. (Or it keeps old problems if a fix is prevented)
In the interest of avoiding future issues (and in the interest of utilizing the ability to disable the component in the only setting where it would likely be used), it would be preferable if this component was disabled by default if it isn't already.

This can be resolved as fixed. 1.5.0.14

This can be resolved as fixed. 1.6.1

Can somebody resolve the following;

this as a duplicate of MCPE-34694
MCPE-34750 as fixed in 1.6.1
MCPE-34844 as fixed in 1.5.0.14

You misunderstood, I was agreeing with you. I already saw the video.
They should not be able to move like that, but they currently are.
Therefore this is a bug and you were correct in having reported it.

Just to clarify, the Zombies that were moving at supersonic speeds hadn't been altered by commands or an Behavior Pack, right?

For future reference users with [Bot] in their name are robots / simple AI.
You may also find this helpful for the future, the mods (ai and human alike) around here can be a bit... quick to make judgement.
Bug Reports Guide

You probably found something that is called a Zombie Village.
They shouldn't move at supersonic speeds though.

Semi-unrelated: It is odd that the dragon AI is based on coordinates.
You'll notice that the dragon always goes near X:0 Y:? Z:0. Which would also be the center of the end.

This would also explain how some people have reported ender dragons coming out of the ground.
Most overworld ground level is above the Y for the ender dragon.

How does the ender dragon function on Java? Does it always fly to the center of a world?

According to the feedback site itself, this issue is now considered a bug.
https://feedback.minecraft.net/hc/en-us/articles/360005029872-Previously-Considered-Feedback

I was able to download one of the packs at the time many people reported being able to download them again.
Me, thinking that the issue had been fixed, deleted the pack for storage space.

Later I tried to download the pack again and the download failed. Now the download consistently fails.
I suppose I shouldn't have deleted it after it had finally worked, but the download should have continued to work anyway.

Not an issue after the 1.5.1 Hotfix, the patch notes have been replaced.

Download keeps failing.

This combined with MCPE-33868 is making managing the inventory very sluggish and frustrating.

The problem isn't the packs themselves.
It's packs purchased on the legacy Switch eShop, not being fully considered as purchased for Bedrock.

If the packs are purchased on Bedrock they will work properly.
However doing so is a redundant purchase that is not fixing the problem.

My best guess is that this issue is caused by a failure in the authentication process for purchased items.

You'll notice that something such as worlds purchased through the Store are unusable if you do not have an internet connection.
Even when they are downloaded to your console they retain a locked icon to indicate that you must connect to the internet in order to access.
I assume it is the same for Xbox Live purchased textures and other content
(Might I add that is foolish considering that the Switch is portable and games that arbitrarily require an internet connection will suffer for that.)
Obviously this is done to prevent piracy, but I feel that this would affect common players more than pirates.
(Especially considering the trouble they would have to go through for a $4-ish resource.)
(Something tells me that they would rather play on Java where textures are free anyway.)

The way that paid world content is accessed implies that the same may be done for other types of content.
That would mean that everytime you load up the game it is connecting to the Xbox Live account to check if the packs are purchased there.
But for whatever reason packs purchased on Legacy Switch have been stated to not be usable on devices other than Switch for Bedrock.

So then that means that when the game goes to authenticate the purchase via the Xbox store, it will find that there was no purchase for the product because the purchase occurred on the Switch eShop. Which would mean that devs intended for content purchased on legacy Switch to be available on Switch Bedrock, but then didn't make an acception for the authentication process. My theory is supported in that users who have purchased content once available to Switch Legacy on Bedrock have had no issues. (Presumably because that is the native and intended behavior of the authentication process.) If the authentication process should fail for a texture, it makes sense that the texture pack would be blocked and begin pulling random textures from the loaded memory including the pink-block error texture we have seen very often, font files, controller tooltips, commandblocks, etc.

If what I suspect is true, then there are two options to fix this;
1) Sync Switch Legacy edition purchases with Xbox Live purchases so that early adopters are compensated, which would also improve Nintendo/Microsoft user relations.
2) Give the authentication process an exception for Switch Legacy DLC.

I just tested this after the latest update and it seems to be working properly again.

MCPE-34633
Please search before making new reports.

To clarify, the images attached to this report do not match the original issue described.
The biggest difference being that we are able to see other players in the join tab but attempting to join always provides the same error.

The issue was intended for Online play, rather than local. So something like half of the previous comment applies here.
The issue described here also does not affect Legacy Console (MCCE).

Take this with a grain of salt:
My best guess is that the original report has something to do with the regions players are playing in.
I have been unable to connect to any players outside of the U.S. with only Switch consoles present in the game, though I have also had problems with connecting to U.S. players but they happen less often. Again, this issue only happens in this version of Minecraft. Bedrock / BTU / (just) Minecraft.

Thankfully End Crystals don't cause damage when they explode, but beds in dimensions other than the overworld will.

I have been struggling with this issue as well. -It makes navigating the inventory and menus feel very sluggish and unnecessarily time consuming.

It turns out that the cursor does change the sensitivity, but the fastest speed seems capped at a very low speed. I set it to 200% and it is just barely moving across the menus. To change the sensitivity of the camera (not for menus) there should be a different option near the broken one that currently works.