|
Bugs
Jan 11, 2013 21:02:07 GMT -5
Post by starfixer on Jan 11, 2013 21:02:07 GMT -5
Two bugs, one somewhat recent and one since last release 1. This one is somewhat recent. On rare occations after fighting a ship and taking damage I will go to a stardock to repair just to realize that my ship damage is gone! 2. This one is since last release. I will g to a stadock, press new ship plan, then press the back button on my phone and press new ship plan and the game will freeze and a pop-up will come up tellin me to force close. Apon doing this, I will go back to that planet to fnd any cargo purchased or any damage repaired is now undone, and when I go into the stardock all ships have "purchase" grayed out. When exiting and coming back to planet, "puchase" is no longer grayed out for ships
|
|
|
Bugs
Jan 11, 2013 21:05:18 GMT -5
Post by Cory Trese on Jan 11, 2013 21:05:18 GMT -5
Thanks!
|
|
|
Bugs
Jan 11, 2013 21:19:05 GMT -5
Post by Cory Trese on Jan 11, 2013 21:19:05 GMT -5
If you are getting a Force Close dialog, can you send a log?
That one should be easy to fix if you can log it, we're not getting any reports of this and it isn't present in the latest release on Google Play.
VERY happy to patch for just your device if we get a log that shows the crash.
Impossible to fix for me right now since it doesn't crash, no one else has reported in Play or via e-mail.
|
|
|
Bugs
Jan 11, 2013 21:29:36 GMT -5
Post by starfixer on Jan 11, 2013 21:29:36 GMT -5
I want to but it only happens once in a while. I tried keping logcat on and waiting, but after 10 minutes it was longer than the ST boarding code. I'll keep trying to log it. Hopefully I'll get it eventually.
What about the other one where after the battle damage is magically repaired? Can you find the problem with that cause that one is REALLY rare
|
|
|
Bugs
Jan 11, 2013 21:44:34 GMT -5
Post by Cory Trese on Jan 11, 2013 21:44:34 GMT -5
I want to but it only happens once in a while. I tried keping logcat on and waiting, but after 10 minutes it was longer than the ST boarding code. I'll keep trying to log it. Hopefully I'll get it eventually. What about the other one where after the battle damage is magically repaired? Can you find the problem with that cause that one is REALLY rare Nope, couldn't find either one. Could be Android file I/O issues, I've seen I/O failures in your logs before related to other applications blocking ST from writing the saved game, which causes things to revert because ST is a good Android application with no permissions.
|
|
|
Bugs
Jan 11, 2013 21:50:40 GMT -5
Post by starfixer on Jan 11, 2013 21:50:40 GMT -5
So what's your suggestion?
|
|