[MCPE-14206] Crashes on multiplayer on iPhone and iPad Created: 20/Apr/16 Updated: 21/Aug/17 Resolved: 21/Aug/17 |
|
| Status: | Resolved |
| Project: | Minecraft (Bedrock codebase) |
| Component/s: | None |
| Affects Version/s: | 0.14.1 |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Lisa Stevens | ||
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Confirmation Status: | Unconfirmed |
| Platform: | Tablet - iOS - iPad Pro |
| Description |
|
Playing Minecraft PE 0.14.1 on the following devices: iPhone SE, iOS 9.3.1 Game is hosted on iPad Pro. When I state the app 'crashes', it quits without warning and has to be reopened. iPhone SE and iPad Air 2 join game. iPad Pro app sometimes crashes when iPhone SE or iPad Air 2 join, and almost always crashes if one device is already connected and the second then joins. Also seemingly random crashes on all devices throughout play - no consistency in crash causes, just happens after a while playing. Crashes happen most frequently when iPhone SE is joined and less so between just iPad Pro and iPad Air 2. They are, however, happening with such frequency that the game is nigh on impossible to play properly as no proper progress can be achieved before yet another crash. Following crash, when iPhone SE or iPad Air 2 try to rejoin game, quite often the host doesn't appear in the world list, and only reappears after the drawn out process of quitting app and often restarting device. All hardware and software is up to date on all devices. All hardware is joined to same wifi network. We always kill all other apps before running Minecraft on all devices, so Minecraft is the only active app running on each device. |
| Comments |
| Comment by [Mojang] Mega_Spud (Jay Wells) [ 21/Aug/17 ] |
|
This ticket has been resolved as 'Cannot Reproduce' as it has not been updated recently (1 year+) |
| Comment by AMAN4700 [ 08/Aug/16 ] |
|
Please respond and add the current version if you can reproduce this issue. |
| Comment by Lisa Stevens [ 03/May/16 ] |
|
This has NOT been fixed in 0.14.2. Still happening across all devices. |