[MCPE-15504] Grass blocks corrupt when quitting MCPE without quitting to title Created: 15/Jun/16  Updated: 21/Aug/17  Resolved: 21/Aug/17

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 0.15.0
Fix Version/s: None

Type: Bug
Reporter: Geoff Stillwell
Resolution: Cannot Reproduce Votes: 0
Labels: None

Attachments: JPEG File corrupt_grass_blocks.jpg    
Confirmation Status: Unconfirmed
Platform: Tablet - Android - Amazon Kindle Fire HD

 Description   

Grass blocks are corrupted when quitting MCPE without quitting to title

The corrupted world stays corrupted even after a reboot. All new worlds created after this event are corrupted from the start. A reboot of the device cures the problem for new worlds created after the reboot, but pre-existing corrupted worlds remain corrupted.

How to reproduce:
Open a new world in creative
Hit the Kindle menu tab (two lines on right of screen)
Hit the home button - reverts to the Kindle carousel
Tap the Minecraft icon to get back into the world
Grass blocks now corrupted, see snapshot.

Also occurs when:
Open a new world in survival
Hit the Kindle menu tab (two lines on right of screen)
Hit the back arrow to show Game Menu
Hit the Kindle menu tab again (two lines on right of screen)
Hit the home button - reverts to the Kindle carousel
Tap the Minecraft icon to get back into the world
Grass blocks now corrupted.

[No matching issues found when searching for 'MCPE unresolved grass blocks']



 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 Colin Macc [ 15/Jun/16 ]

Yes we've had this happen on our kindle fire hd too but could not work out what caused it

Generated at Sat Jan 11 15:07:55 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.