To reproduce every time on iPhone 5, with freshly updated iOS 6.1
1 No other apps running 2 Launch mcpe 3 create world named bugtest with seed bugtest 4 survival mode peaceful 5 do not step forward 🙂, turn around 6 break some blocks, place some blocks 7 pause 8 quit to title 9 home key 10 double click home key 11 select mcpe 12 start game 13 select bugtest 14 repeat steps 7 to 13 four or five times at least 15 place some blocks, break some blocks retaining some in inventory 16 repeat steps 7 to 13 17 observe that the most recent placed and broken blocks are gone
Once you get into this state none Of your changes will EVER save until you double click home, press and hold mcpe, click on the minus to kill the app and then relaunch it.
A (very tedious) workaround is to quit to title, kill the app, and relaunch whenever you pause. Never try to reload app from Background.
I hope mojang will take this Bug very seriously, since it is a "loss of user data" bug. That should be right up there behind "personal injury" and "Security exploit". Indeed since this smells like an "uninitialized data" big, it has some risk of potential security exploit.
Paul Drews
To reproduce every time on iPhone 5, with freshly updated iOS 6.1
1 No other apps running
2 Launch mcpe
3 create world named bugtest with seed bugtest
4 survival mode peaceful
5 do not step forward 🙂, turn around
6 break some blocks, place some blocks
7 pause
8 quit to title
9 home key
10 double click home key
11 select mcpe
12 start game
13 select bugtest
14 repeat steps 7 to 13 four or five times at least
15 place some blocks, break some blocks retaining some in inventory
16 repeat steps 7 to 13
17 observe that the most recent placed
and broken blocks are gone
Once you get into this state none
Of your changes will EVER save until
you double click home, press and
hold mcpe, click on the minus
to kill the app and then relaunch
it.
A (very tedious) workaround is
to quit to title, kill the app,
and relaunch whenever you pause.
Never try to reload app from
Background.
I hope mojang will take this
Bug very seriously, since it
is a "loss of user data" bug.
That should be right up there
behind "personal injury" and
"Security exploit". Indeed
since this smells like an
"uninitialized data" big, it
has some risk of potential
security exploit.