0

The app has MainActivity and NextActivity. User opens the app in MainActivity, then goes to NextActivity.

If user sent the app into background the system may kill the application process.

In logs I see that sometimes when user opens the app again next time the system restarts application process from NextActivity instead of MainActivity. Sometimes It causes one crash

I fixed the crash, but to test the fix I have to reproduce scenario when the application process is restarted from the last opened activity.

I checked and tried suggestions from this SOF questions:

Android Simulator: Easy way to simulate a process restart due to low memory?

Simulate killing of activity in emulator

Simulate low battery & low memory in Android

But every time when I kill the application process on next open I saw that the app restarted from MainActivity.

Roman Markov
  • 3
  • 2
  • If you want to try it without ADB you can minimize the app, go into app settings and revoke any permission. – Pawel May 01 '23 at 22:02
  • @Pawel yes, I tried and it works, thanks! It is the simplest way for our QA team to reproduce and test the issue. – Roman Markov May 02 '23 at 09:44

1 Answers1

0

When I need to check such cases I use this adb command:

adb shell am kill <app_package_name>

and I do it in the following sequence:

  1. Open app screen that I want to check for restoring state.
  2. Move app to background using home button.
  3. Execute the adb command that I mentioned above.
  4. Open app from the recent apps menu.

If app handles restoring state correctly I see the screen from the first step with correct state if not I see incorrect state of the screen, another screen, crash etc.

easy_breezy
  • 1,073
  • 7
  • 18
  • 1
    yes, after check in logs I saw that the app actually restarts from the last opened activity but closes it immediately because of my fix =) thank you for your answer, I made sure that I did right things – Roman Markov May 01 '23 at 21:27