mojira.dev

Productive

Assigned

No issues.

Reported

No issues.

Comments

I'm a previous commenter, but I can also confirm that this issue still persists in the most recent version of Minecraft (1.20.41) while running on the latest iPadOS version 17.1. Device-wise I'm using the M1 iPad Pro hooked up to the LG 4K external monitor, which I mentioned in my first comment here, without a possibility to resize the Minecraft app window from the 4:3 or so aspect ratio to full screen.

This bug can still be replicated on 1.19.81, even after removing the "Recent Apps" and "Dock" from the view through Stage Manager settings. The app window of Minecraft can still be resized, but no matter the size it still stays at a constant 4:3 aspect ratio with the bars on each side, as opposed to being able to jump into fullscreen at the 16:9 ratio of my external monitor. The device I'm using is the 11" M1 iPad Pro with the Magic Keyboard case and an LG 4K external monitor.
Really hoping that some light could be shed on this issue as fixing this bug would give a larger incentive to play more on the iPad version of Bedrock.

Edit: Still affects version 1.20.1.

Edit: Also affects version 1.20.15 on the 11" M1 iPad Pro (running iPadOS 16.6) when it's connected to the Apple Studio Display as its external monitor.

Achievements are still not unlocking on Switch as of 1.19.81.

The bug is still reproducible and present in 1.19.81 on both my iPad Pro 11" (M1) and iPhone 12 without any way of resolving it on my own. It still shows "Download failed. The world size exceeds the maximum downloadable limit of 426.7MB". Meanwhile, even though I have more than enough free storage on my Switch, there on 1.19.81 it says "You are almost out of data storage space!"

This is a shame as I wanted to get my world from my Switch to my iPad, and it seems like even if this part worked and I ever wanted to gather my world back onto my Switch, I would still run into issues.

Edit: The bug is still present on the just released version 1.19.83.

Edit: Still affects the recently released version 1.20.10.

Edit: The bug affects version 1.20.13 as well.