metaed

I can reproduce it in 1.21.20, if that's what you're asking. I have not tried betas.

On this device, manually adjusting the screen Safe Area to a value of around 75% was a decent workaround for me, in both portrait and landscape rotations. Credit to Jarl-Penguin on the Mojira Discord.

A reasonable permanent solution would be to detect the device and limit the value of Safe Area to 75%.

Picture 1 shows the rounded display of a Google Pixel 8 Pro cropping the Main Menu. The crop can be seen obscuring the copyright symbol, and obscuring the minor version segment of the version tag.

Picture 2 shows the effect on the Settings screen. The troubling issue on the Settings screen is that the Back button in the top left corner is hard to trigger. This is partly because some of the touch zone is cropped, and partly because the user's finger is elevated by the adjacent bevel on the corner of the vendor-supplied case. This issue with the Back button applies to every individual Settings page, and also every Marketplace page.

Minecraft 1.20.50, build 19782186

Android 14, build UD1A.231105.004

Pixel 8 Pro

Workaround is to clear cache. Problem comes back later. I have not been logging in to a Realm.

I believe my bug report should be closed as a duplicate of MCPE-149447. On the Pixel 8 platform the workaround is to install com.marc.files from the Google Play Store.

The error "Appearance is taking a long time to load. Proceeding with world generation" appears on my Google Pixel device running 1.20.32 for Android. This happens every time I open an on-device world. I have no resource packs activated – neither at the global level nor at the world level. The error does not impede world loading. After a short dwell time, the message disappears and the world loads.

I can no longer reproduce the error "Download failed. The world size exceeds the maximum downloadable limit of 426.7MB." in 1.19.80 or 1.19.81, on a Pixel 3XL running Android 12. This problem has plagued me at least as far back as 1.17.0. Now I can download a 688 MB Realms backup with no problem.

Unfortunately I can't tell you what changed. I'm still on the same device and don't remember changing settings. I've installed updates as they've come out. But I've reviewed release changelogs all the way back to 1.19.41 and don't see a relevant bugfix announced.

Is this still reproducible by others?

EDIT: Thinking back, one thing I remember doing is cleaning up the old/obsolete directory /games/com.mojang/minecraftWorlds, that was left behind when the Caves and Cliffs update moved everything to /Android/data/com.mojang.minecraftpe/files/games/com.mojang/minecraftWorlds.

So it would be interesting to know if you are an Android user having the 426.7MB problem, whether there are pre-Caves-and-Cliffs files in the old directory, and if so, what happens if you clean those up.

EDIT: Still unable to reproduce, now running 1.20.30, still on the Android platform.

@Blumamu fix was released - 1.19.71 dropped today.

Confirmed bug still present in version 1.19.50.02 for Android.

Confirmed bug still present in version 1.19.50.02 for Android.

Confirmed bug still present in version 1.19.50.02 for Android.

Confirmed still present in version 1.19.41.01 for Android.

Confirmed still present in version 1.19.41.01 for Android.

Confirmed still present in version 1.19.41.01 for Android.

Reply from @unknown: It is not very helpful to continue adding comments like this to bug reports, and it generally just adds clutter and makes it harder to find the important comments. If an issue is not mentioned in a changelog, it is unlikely to have been fixed, so there is no need to comment about it.
However, if you want to ensure that the Affected Version does get updated, you can submit requests for that on the Mojira Discord.

Confirmed still present in version 1.19.41.01 for Android.

Confirmed bug still present in 1.19.40.02 hotfix for Android. Please update Affects Version(s) field.

Confirmed bug still present in 1.19.40.02 hotfix for Android.

Confirmed still present in 1.19.40.02 update for Android.  Still gives an arbitrary downloadable limit of exactly 426.7 MB unrelated to local device capacity. Tried the new Settings, Storage, Clear Marketplace Cache button, and this had no effect at all on either the problem or the number reported in the message.

The 2022 Mob Vote has ended, yes, I agree. But. There will, one presumes, be future mob votes, and they will be managed by this code in the app, that provides the countdown and opens access to the vote server at the correct local time. So it is still a bug worth fixing between now and the next mob vote.

Confirmed bug still present in 1.19.31.01 hotfix for Android.