Whilst playing the App over the weekend (love it!), we ran into an App rules question. We hit the information/help/rules button (whatever it's called) which took us to the pdf on the SW:IA main site. We looked for an answer and returned to the game. The App reset. Now, once we loaded our save, our progress was back to the correct mission and round (yay!). However, it was top of round where we had been multiple activations in (oh no!). We marked CAHRACTER-ONE has having gone, then it activated a random unit which hadn't previously activated. We were able to adjust, for the most part, but because the Imperial activation block isn't available for recall, we had to improvise how the new enemies attacked when we got back to our game state.

Now, knowing how this happens, we would be prepared to memorize the enemies' attack blocks next time. We could have tried to undo all damage and movement and actions that round (to the best of our memories), but because we'd rolled poorly, we felt as though it would be cheating.

In Mansions of Madness 2, when the App saves, I believe it does so between phases, which are particularly easy to recreate.

I am also ecstatic to find that it saves at least between rounds.

I don't know that this is particularly a bug, but it is something to be mindful of as both players and programmers. I get why it would take you to the website (although that does add internet dependency) to see the rules: it reduces the number of places the rules need to be updated.

You can download the LotA rulebook directly from the IA page outside of the app.

If you can reproduce the issue (use a New Game), I can help you report it. (Also specify which platform.)

(You can also contact FFG through https://www.fantasyflightgames.com/en/contact/support/ (Software department) with as exact report about the issue and how to reproduce it.)

I've printed out the rule book specifically so I wouldn't have to switch apps. But I find it strange that they didn't properly account for people switching out of the app to access the rules

1st, running on iOS (both pad & phone). 2nd, yes, once I finally got time to mess around in the app, I was able to recreate the issue.

To trigger it, it needs to be midway through a round. Then, if you navigate away from the app and it "goes to sleep," when it reloads, it will be at the top of that round.

I say "go to sleep," but what I mean is that the app looses CPU priority and it goes passive. When it comes back, the app must be reloaded and you must resume the save file.