|
Post by ender78 on Sept 18, 2008 21:20:29 GMT -5
I have run into this problem twice now , upon resume game which was quit using home button, instead of being prompted for the "Buy Challenges/Keep Mining" screen, I hear music and get a blank screen, game does not start.
|
|
|
Post by theconfuzed1 on Oct 3, 2008 1:00:29 GMT -5
I've had that happen once. After quitting the game though, and restarting, it never happened again, so I didn't think much of it at the time.
Did this happen to you twice in a close proximity of time, and both times on the current version of the game?
When it happened to me, it was a couple versions ago.
|
|
|
Post by burtosis on Oct 3, 2008 10:14:44 GMT -5
|
|
|
Post by vexedgirl on Oct 3, 2008 11:53:37 GMT -5
I have had the same issue several times now, ever since I maxed out my levels.
|
|
|
Post by Danielle Cassley on Oct 4, 2008 3:55:27 GMT -5
Please post something on how to reproduce.... sounds like it starts with "max out your levels"...
|
|
|
Post by burtosis on Oct 4, 2008 11:55:52 GMT -5
I have seen this the most times when I open up AF, then am taken to a mining menu screen (dosen't seem to matter which - inventory, community) where i was last. Then, I try to go to mine and it gets the screen. Though it also happens at other times when you would expect a keep mining/goto store menu.
|
|
|
Post by burtosis on Oct 13, 2008 12:41:42 GMT -5
Wanted to add that if you have a chain stored up when you exit, this bug does not happen. Only if you have nothing currently happening (other than the blocks slowly rising) does this bug hit.
Also, I have tried exiting to the map instead of the mine, and a different aspect of this bug hits. You can't select anything, such as the mine or tower, and this locks up the game since you are effectively stuck on the map screen. Exiting and re-entering appears to fix the problem - except if you re-enter back to the mining option screens when starting up - which appears to be the main cause of this bug (at least once levels are maxed).
|
|
|
Post by burtosis on Nov 14, 2008 19:50:10 GMT -5
I just downloaded version 1.2.1 and this is now fixed for me!
|
|
|
Post by burtosis on Nov 17, 2008 21:17:08 GMT -5
Allright, I was mistaken. THe bug is still here.
For more info, see the other thread in game bugs.
|
|
|
Post by eliu87 on Nov 20, 2008 23:39:14 GMT -5
I'm pretty sure that the game has been coded not to tell you to go to the store when you've maxed out, but that's it, leaving the game with no code to execute?
|
|
|
Post by burtosis on Nov 21, 2008 10:50:36 GMT -5
First off, unless you are 8/8 and 4/4 in every category this bug will never hit, at least I have never seen it when my character was not maxed out.
Well, it still prompts you to "you must complete your existing challenges to level up." Then has options to "Buy challenges" or "keep mining" in AF code version 1.2.1
The bug does not happen immedieatly after a re-install. Something about opening other apps seems to be necessary for it to hit me. After that if you leave AF from a mining menu, then come back in by opening AF again, then when you go to the mining screen you just get a black screen with the music. If you try to go to the map, then the map does come up, but you can't click on anything. Outside of that everything appears to be normal. To fix this if you left the mining screen you have to then exit and re-enter and then you go straight to the mining screen (whew finally!). If you exit the map screen, then re-enter to the map you can then click on things normally. This happens every time and 100% of the time for me.
If you do the above from the mining screen, but open another app after exiting AF, but then close that app and continue, you are instead taken to the mining menu screen to start all over again. If you are on the map screen, opening an app makes no difference.
So it must be something in the code that is buggy and partially pops up the window locking up the game. These features of how it works should give a good clue to anyone working on the code how to track down and fix it.
Again, I tested this all with 1.2.1 just now, so I am sure this is how it works in the latest update.
|
|