mojira.dev

Matt Gadda

Assigned

No issues.

Reported

No issues.

Comments

This issue seems to be resolved in 1.16.220.

@schleppy have you signed in again? 

Minecraft version: 1.16.210

Model Name: iPad Pro (9.7-inch)

Model Number: MLMV2LL/A

iOS Version: 14.4, 14.4.1, 14.4.2

Internet status: Wifi and Offline

Game login status: signed in

Successful launch cycles before failure: independent of number of launches or play time. Seem correlated with sign in status, however.

Deleting the xal directory seems to eliminate the crash, presumably because it signs me out. But immediately after signing in the app crashes. (tap sign in, authenticate with Microsoft, crash) and the app crashes on load thereafter. 

 

 

Also, reinstalling Minecraft resolves the issue but only temporarily. Within a few hours of play over several days the app is back in a state where it will not load.

I have not seen such failures prior to Minecraft version 1.16.210, but they did not coincide with the update to that version. The behavior started about two weeks following when it was auto-updated from the App Store. If 1.16.210 introduced a bug, there must be some other condition that was not present on the device prior to the period documented in the crash log I uploaded. 

The crash was present in iOS 14.4 and 14.4.1. I have not tested it on 14.4.2 yet.

It's hard to say from this description if reporter's issue is the same what I've started experiencing. But 1.16.210 also crashes on start up for me 100% of the time on my iPad Pro 9.7-inch. I've attached an example crash log: 

[media]

The behavior is that the app displays its loading screen (tiny gray bars) until the last few bars remain at which point the app experiences an EXC_BAD_ACCESS and is terminated. 

I've double checked that the reference ping above does have an alpha transparency channel and still reproduces the issue.

I have confirmed that it is still reproducible using the images you linked above with Minecraft version 1.16.1 running on iOS 13.5.1 using an iPhone 11 Pro.

This issue is also reproducible in Minecraft (version 1.14.60) for iOS/iPadOS (version 13.4.1).

Is there a time estimate for a fix?