Nick Wade
Comments
@unknown, I've done clean installs on both my kids' iPad Mini in recent days, with no discernible difference.
I know it might be hard to get hold of an older model iPad hardware device for proper debugging but it may be prudent to do so. Minecraft Pocket Edition was rock-solid. Whatever this replacement is, it's causing some issue on these older less capable devices.
If I have a device hooked up to XCode can I catch useful crash logs for you? Is there a debug mode r can enable to generate useful logs? Or a debug version you'd have us try?
OK MoJira team @unknown, at my house we have two iPad Mini both model A1432. One running iOS 9.3.5, one running iOS 8.1.1 (I held one back to compare / contrast differences. Both running Minecraft 1.2.5 as latest from the App Store. The kids get random lagginess they call "funky" in any single player levels after a time. They get random crashes in the same manner. There are no Xbox accounts as they're too young (4 and 6). Both iPads are wifi internet connected.
Alright Microsoft and Mojang, this has gone on long enough. While we realize that the unified game across platforms is a great goal, you are also contractually obligated to provide the purchased content under the Apple App Store T&C's, https://www.apple.com/legal/internet-services/itunes/us/terms.html, specifically "If technical problems prevent or unreasonably delay delivery of Content, your exclusive and sole remedy is either replacement of the Content or refund of the price paid, as determined by Apple." (emphases mine)
You are clearly aware that the game crashes regularly. There is no fix provided in a time that might indicate commercially reasonable efforts. This likely constitutes a breach of the provision to actually provide the content without technical problems preventing such. You have not provided information on when we can expect a fix for iPad Mini and other mobile devices.
Now, your own terms state that your games will contain errors and bugs however this length of time without a working update for us is totally unreasonable. I do not believe any of this will supersede Apple's terms: https://account.mojang.com/terms
tl;dr - I'm moving into refund process now, sadly.
By the way; along with two guys from Code.org (Brian and Will), I am the third guy who started the Hour of Code Minecraft tutorials that eventually led to these: https://code.org/minecraft. That start was a project at Atlassian in 2014. The real ones you see today were published a year later in 2015. We are huge supporters, and my kids played with deep enthusiasm - until this fiasco. Now they cannot sustain play at all and are losing interest in Minecraft. The entire Minecraft club at our elementary school is also experiencing same; both the crashing and the slow loss of interest. This whole situation is DEEPLY disappointing.
Dear Mojang, may I suggest you add a workflow status Tracked elsewhere. None of the duplicates are actually resolved at this stage, and this issue ticket is the controlling ticket.
Source: I am an Atlassian
Also another comment vote for this issue; both iPad Minis in our home and the entire elementary school fleet of iPads suffers from this random frequent crashing.
Also note that a great many reviews on iTunes App Store refer to this laggy / crashing issue https://itunes.apple.com/us/app/minecraft/id479516143?mt=8
Also team - as best practice you may want to consider using a Status other than Resolved when you're closing a Jira ticket as a duplicate of something else. Source: I work at Atlassian
Device logs so far via XCode show a lot of "Unknown" crashes with limited information about each. Not sure that's going to be useful, but let me know.
Additionally I just clean reinstalled 1.2.5 today and the boy played a flat world with no crashes for almost 90 minutes.