Skip to content

Conversation

@jcassidyav
Copy link
Contributor

I was able to reproduce #397 by:
Enabling in Developer settings on the phone the setting "Don't Keep activities, Destroy every activity as soon as the user leaves it".
which I believe simulates the case that Android will kill an activity in the background due to memory pressure

To reproduce the issue:

  1. Set the above developer setting.
  2. Launch the demo-view app.
  3. Goto Tabs
  4. Send it to the backgound.
  5. Bring it into foreground again.

While this solves particular case, there appears to be similar issues in other scenarios which this does not address,

e.g. ( after this fix is applied)

  1. Launch the demo-view app.
  2. Goto Tabs
  3. Send it to the backgound.
  4. Bring it into foreground again.
  5. navigate back to the menu.
  6. navigate to Tabs again
  7. Send it to the backgound.
  8. Bring it into foreground again.

@farfromrefug
Copy link
Member

@jcassidyav thanks for this. Dont really have the time to test it though. I will release it though
Will try to take a look at this later.
THanks

@farfromrefug farfromrefug merged commit ff9fdc0 into nativescript-community:master Feb 17, 2023
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

Successfully merging this pull request may close these issues.

2 participants