Hi,
i have a curious problem here.
When I run the game (both as app on device, or the unity player on desktop) the game initializes, the primary FSM triggers the "START" state, and then all of a sudden it fires "APPLICATION PAUSE" without finishing running through the states that are connected to the startup/init routine.
The "APPLICATION PAUSE" event is caught in the same FSM by another state that handles my pause function.
I implemented a nasty workaround that loops back to the start state chain, when the app is initializing via a bool test. - But that's not really an acceptable solution.
So my question is: why is "APPLICATION PAUSE" automatically triggered while initializing all the time? Is this "normal" Android app behavior? or is there something else wrong with my project/the unity editor or anything abnormal?