Should someone update the list of affected versions to include 1.13.1 on this bug report?
Can we get an update on whether the devs have been able to replicate this issue?
Thanks Joshua!
Original version of this post includes quite a few comments, including some from @mega_spud, that demonstrate additional issues with the hopper hitbox. See: https://bugs.mojang.com/browse/MCPE-13758
@Edd has a nice idea. I hope a fix will be available soon for iOS players. If this goes on much longer, Mojang should consider refunding this month’s Realm subscriptions to make up for pushing an update that makes the game unplayable.
First report of this bug appears to be https://bugs.mojang.com/browse/MCPE-54500
First report of this bug appears to be https://bugs.mojang.com/browse/MCPE-54500
Also happening to me after updating to 1.13 on my iPad3. I had opened Minecraft 1.12 and was notified of the update when I opened my Realm, so I said yes to the prompt to check for updates. The app switched over to the App Store, I clicked Update on the Minecraft app, and waited while it installed the update. But ever since then, I get exactly the behavior described in this ticket. Mojang screen, empty white screen, then crash out to iPad home screen. The app is still running in the background, but when I switch to it the screen is still white and then it kicks me back to the home screen. I’ve tried restarting iPad and even did a hard reset. Behavior is identical in all cases. RIP Minecraft.
Also happening to me after updating to 1.13 on my iPad3. I had opened Minecraft 1.12 and was notified of the update when I opened my Realm, so I said yes to the prompt to check for updates. The app switched over to the App Store, I clicked Update on the Minecraft app, and waited while it installed the update. But ever since then, I get exactly the behavior described in this ticket. Mojang screen, empty white screen, then crash out to iPad home screen. The app is still running in the background, but when I switch to it the screen is still white and then it kicks me back to the home screen. I’ve tried restarting iPad and even did a hard reset. Behavior is identical in all cases. RIP Minecraft.
Also happening to me after updating to 1.13 on my iPad3. I had opened Minecraft 1.12 and was notified of the update when I opened my Realm, so I said yes to the prompt to check for updates. The app switched over to the App Store, I clicked Update on the Minecraft app, and waited while it installed the update. But ever since then, I get exactly the behavior described in this ticket. Mojang screen, empty white screen, then crash out to iPad home screen. The app is still running in the background, but when I switch to it the screen is still white and then it kicks me back to the home screen. I’ve tried restarting iPad and even did a hard reset. Behavior is identical in all cases. RIP Minecraft.
Also happening to me after updating to 1.13 on my iPad3. I had opened Minecraft 1.12 and was notified of the update when I opened my Realm, so I said yes to the prompt to check for updates. The app switched over to the App Store, I clicked Update on the Minecraft app, and waited while it installed the update. But ever since then, I get exactly the behavior described in this ticket. Mojang screen, empty white screen, then crash out to iPad home screen. The app is still running in the background, but when I switch to it the screen is still white and then it kicks me back to the home screen. I’ve tried restarting iPad and even did a hard reset. Behavior is identical in all cases. RIP Minecraft.
Also happening to me after updating to 1.13 on my iPad3. I had opened Minecraft 1.12 and was notified of the update when I opened my Realm, so I said yes to the prompt to check for updates. The app switched over to the App Store, I clicked Update on the Minecraft app, and waited while it installed the update. But ever since then, I get exactly the behavior described in this ticket. Mojang screen, empty white screen, then crash out to iPad home screen. The app is still running in the background, but when I switch to it the screen is still white and then it kicks me back to the home screen. I’ve tried restarting iPad and even did a hard reset. Behavior is identical in all cases. RIP Minecraft.
For reference, a ticket for the hopper hit box issue now exists at: https://bugs.mojang.com/browse/MCPE-47541
In terms of Java/Bedrock edition parity, note that this issue was fixed long ago for the Java platform. Also note that in Bedrock we can click items visible through gaps in stairs and slabs and even between chests, so it’s inconsistent behavior within the Bedrock codebase to not be able to reach items that are visible behind a hopper’s funnel.
The worst thing is this functionality is (1) already in the instruction book and (2) already in the game when it comes to inventory of chests, hoppers, furnaces, shulker boxes, etc., etc., etc. The functionality already exists: just make it work for the crafting interface. Please???
Happening to me in 1.12.1 on Realms running on iOS. Never had this bug in any previous Realm world, but now it happens pretty much every time on this one. So much for my shortcut to the XP grinder.
Portal A and B are only about 10 blocks apart on the nether-side, and they are the only two portals in the world at this point. It doesn’t matter which one I go through first, but when I try to return from the nether to the over world, I get the infinite “loading terrain” screen. I discovered that killing the game and re-logging does not solve the problem (still infinite “loading terrain” screen), but Closing the realm by taking it down/offline and then re-Opening it fixes the problem. After doing that, I always end up spawning on the surface above the destination portal, even though both portals are under ground. This bug makes using the nether as a shortcut unworkable. Really frustrating...
Note: At some point the hopper hitbox was changed / fixed for Java edition. See: MC-6435. Be great to see the same fix applied to Bedrock edition.
Hopper hitbox is so annoying. You can see past its funnel, but you can’t click anything behind it. I’d put this near the top of the list of small changes that would reduce frustration by a huge amount.
It's not just an issue with workstations and having enough (extra) beds. Villagers are not entering the "willing" state the way they should. I'm using iOS 1.11. See MCPE-44512 and MCPE-45194.
Looks like 1.13.2 fixed it for both iPad2 and iPad3 in our house. Thanks for pushing out an iOS only fix to correct the problem!