I've gotten pretty far in one of my saves before the stopped working. Every time I tried to load my vault the game will crash. I first tried clearing google services data and google play games data. It still didn't work. Than I saved my file on to the cloud and I cleared all data from the app itself. After recovering my vault from the cloud I tried to load it but it still crashed. I then created a new vault which I was able to load without the game crashing. I believe that my save has been corrupted some how and I want to know if its possible to restore it or create a new file with around the same amount of progress. My google account is [email protected] and my save file was named 864. It was saved in the first slot.


Thank you if you read this,


Ben Moore

I have the same problem with one of my vaults. I have 80 rooms (and almost no space left) and 200 dwellers, with one dog and one Mr. Handy. My vault crashed right in the middle of an attack by mole rats - I had some rats in empty rooms and they seemed to be leaving - and have some dwellers been successfully killing other rats in 2 rooms. I should have got credit on a task (combat 5 mole rat attacks with zero casualties), but just there the game crashed and I was not able to load the vault since then. My other 2 vaults are working correctly.

Restarting the phone, emptying cache, starting from the cloud or re-installing the app have not worked at all. The bug also happened with an Android emulator on my laptop. I have a Sony X-Peria Z3 phone, which should be more than enough to handle the app.

I also get a corrupted loading screen with this vault, before it crashes. Sometimes I see that Mr. Handy has collected food/water from a nuka-cola-room, before the app crashes. I have filled out a bug report some days ago (25th of December), but have received no feedback since then.

That objective bugs out on people. If you can get the vault to load and run for a couple seconds before it crashes, X out that objective.

I think someone else here also saved a vault with that bug by loading it up on a device with v1.2 of the game, since that version isn't bugged.