Can not perform this action after onSaveInstanceState

I've faced this problem sometimes but I've never written about it. It's very interesting because it proves that the Android avoid at all costs lose the state of the activity. This error commonly happens when you try to commit a fragment transaction after the onSaveInstanceState() be called, in other words, when you do it in … Continue lendo Can not perform this action after onSaveInstanceState

Saving Instance State…again

I've posted sometimes about save instance state on activities (in portuguese), but I could observe that I've writen that Android OS can kill your process when it needs memory, so the activity can be destroyed anytime. I've written too that when it happens Android will give a chance to developers finish any threads or connections … Continue lendo Saving Instance State…again

Rotação do Dispositivos e a Recriação da Activity

Your application should be able to restart at any time without loss of user data or state in order to handle events such as configuration changes or when the user receives an incoming phone call and then returns to your application much later after your application process may have been destroyed. Por padrão, quando alguma … Continue lendo Rotação do Dispositivos e a Recriação da Activity

Activity And The Saved Instance State

When we are using an application, fairly easily may happens to go to another one to do something, for example see a message, and after we come back. So, in this common situation, when we come back to the first application, we are expecting to see all thing exactly as we left. Imagine if you … Continue lendo Activity And The Saved Instance State