Same issue here. Two iPad 6th gen (2018, A10, iPadOS 17.7.11). Since the 26.50 update, the app shows the launch image, then a white screen, then crashes to the home screen after a few seconds. Worked fine on 26.45.
Already tried: deleting and reinstalling, restarting, airplane mode. No change.
Attached the crash dump (.dmp) and .crashedsession file from the Minecraft folder on the iPad.
Crashing thread calls abort() (pthread_kill) from inside Metal.framework, with AGXMetalA10 (the GPU driver) on the stack, called from minecraftpe. Looks like Metal hitting a fatal error during renderer init.
Main scene stack is empty, so it crashes before the title screen loads.
Session tag dynamicTexturesEnabled = true. Could be the common factor, since others see this on iOS 18 too.
Unsymbolicated minecraftpe return addresses from a stack scan of the crashing thread: +0xcb825e8, +0xcb8b864, +0xcb60a88, +0xcb83838, +0xcb5b1e0.
Kids can't play at all right now, and there's no workaround because the app never gets far enough to change settings.
Same issue here. Two iPad 6th gen (2018, A10, iPadOS 17.7.11). Since the 26.50 update, the app shows the launch image, then a white screen, then crashes to the home screen after a few seconds. Worked fine on 26.45.
Already tried: deleting and reinstalling, restarting, airplane mode. No change.
Attached the crash dump (.dmp) and .crashedsession file from the Minecraft folder on the iPad.
Session ID: f5f5e5a4-c3d2-4cc8-b787-5a5eee45d7f0
Build: 1.26.50, commit df6459772ad9, branch r/26_u5, flavor Publish
What the minidump shows:
Crashing thread calls abort() (pthread_kill) from inside Metal.framework, with AGXMetalA10 (the GPU driver) on the stack, called from minecraftpe. Looks like Metal hitting a fatal error during renderer init.
Main scene stack is empty, so it crashes before the title screen loads.
Session tag dynamicTexturesEnabled = true. Could be the common factor, since others see this on iOS 18 too.
Unsymbolicated minecraftpe return addresses from a stack scan of the crashing thread: +0xcb825e8, +0xcb8b864, +0xcb60a88, +0xcb83838, +0xcb5b1e0.
Kids can't play at all right now, and there's no workaround because the app never gets far enough to change settings.