Just now saw that my Pixel 8 Pro is offering an "update" to 1.21.31 from 1.21.50.20. It should install, but as previously mentioned, once installed, any worlds opened on the 1.21.50.20 beta will become inaccessible until the full 1.21.50 release.
Please see the comments on MCPE-187297.
I want to advise anyone not participating in the beta to turn off auto updates for Minecraft for now. Even if you choose not to update manually, there is a chance that the auto-update may activate and install the beta version (this happened to my Pixel 8 Pro)
Are you on the 1.21.40.22 Preview or the release 1.21.30 version? Dyed bundles were added in the 1.21.40.22 Preview and are not in the 1.21.30 release.
This appears to be fixed in 1.21.40.20
I am unable to reproduce this in either 1.21.23 or 1.21.30.25
Affects 1.21.30.24
I get the same message on a refurbished Galaxy Tab A7 Lite (though it being refurbished should make no difference), updated to Android 14.
Affects 1.21.30.22
Affects 1.21.20.23
Sorry for not responding sooner, I spent a few days trying to get as much information as I could so that we can reproduce this on multiple computers.
I could reproduce this with multiple wireless Logitech USB keyboard and mouse combinations, using a mix of dongles (to make sure none of the dongles are defective), with the combinations using either the same dongle or two different dongles (one for the keyboard, and one for the mouse) plugged into a USB 2.0 hub. I could not reproduce this with two dongles plugged directly into the PC (either on the front panel or the motherboard). In all combinations, testing was done with fresh Alkaline batteries only, and no rechargeable batteries were used.
In every combination, all the mice tested were optical.
Lifting the mouse does remove the keyboard hang.
I don't know of anything else that can be done with a consistent effect on the hang.
So far, the only indicator is that the keyboard and mouse have to share a USB port in some way.
Affects 1.21.2
@unknown I've noticed that if I plug my USB keyboard and USB mouse into a USB 2.0 hub plugged into my PC (that I built), the same issue occurs. Could they possibly be related? I've only tested with two USB 2.0 hubs, but with a few different brands of keyboards and mice. I'll have to test with other Windows 11 PCs that I have.
Affects 1.21.20.21
This appears to be fixed in 1.21
Affects 1.21.10.20
Possibly related to MCPE-178759
This issue has been fixed in a pre-1.20 update to Minecraft.
I regularly use third-party apps to determine the target API of certain other apps when testing apps with different versions of Android. In this instance, I used it to determine Minecraft's target API and made a discovery that might be relevant to the issue. Minecraft version 1.20.73 targeted API level 31 (Android 12), when downloaded through the Google Play Store. However, Minecraft version 1.20.80 targets API level 34 (Android 14).
Unfortunately, I do not own an Android 14 device, so I can't confirm this for myself, but anyone facing the incompatibility prompt before shouldn't be on 1.20.80 at least according to my discovery. If anyone owning an Android 14 device can install 1.20.80 through the Google Play Store, please let me know if you are getting the prompt after installing 1.20.80 and Android 14.
Fixed in 1.21.51