Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stages of the Activity Lifecycle: Android Basics with Compose #29

Open
peterMonteer opened this issue Mar 5, 2024 · 1 comment
Open

Comments

@peterMonteer
Copy link

In which task and step of the codelab can this issue be found?
4. Explore lifecycle use cases

Describe the problem
Following the steps to move the app to the background ( being it by pressing the back button or the home button ) is triggering the onDestroy callback. Tested on 2 fresh emulators with enough memory.

Steps to reproduce?

  1. Start the app on an AS emulator
  2. Follow the steps to move the app to the background
  3. See that onDestroy is called

Versions
Android Studio version: Iguana
API version of the emulator: 34 and 28

@aHardReset
Copy link

As mentioned in the Codelab, the android OS could destroy a background app to recover system resources, in order to avoid that try to close any opened app before doing the exercise, also, can you share your system resources?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants