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

ReOpening android app is cached #17211

Closed
nschurmann opened this issue Dec 14, 2017 · 6 comments
Closed

ReOpening android app is cached #17211

nschurmann opened this issue Dec 14, 2017 · 6 comments
Labels
Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot.

Comments

@nschurmann
Copy link

nschurmann commented Dec 14, 2017

Is this a bug report?

Yes

Environment

Environment:
OS: macOS High Sierra 10.13.1
Node: 8.5.0
Yarn: 1.3.2
npm: 5.3.0
Watchman: 4.9.0
Xcode: Xcode 9.2 Build version 9C40b
Android Studio: 2.3 AI-162.4069837

Packages: (wanted => installed)
react: 16.0.0-alpha.12 => 16.0.0
react-native: ^0.47.1 => 0.51.0

Target Platform: Android (8)

Steps to Reproduce

(Write your steps here:)

  1. Install the app
  2. Open the app
  3. Navigate somewhere like 'products'
  4. Close the app
  5. Open the app
  6. The app will be in 'products' instead af the main scene

Expected Behavior

  1. Install the app
  2. Open the app
  3. Navigate somewhere like 'products'
  4. Close the app
  5. Open the app
  6. The app will be in 'index'

Super easy and replicable steps 😄

@jerameel
Copy link

This is not possible unless you are saving the state.

@nschurmann
Copy link
Author

@jerameel this is the default behaviour in android prior to 7...

@jerameel
Copy link

If you close the app without actually removing it in the "recent apps" it would probably resume its last state as long as android has enough memory to sustain it. This is the default behavior for all android versions.

@stale
Copy link

stale bot commented Feb 17, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions.

@stale stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Feb 17, 2018
@nschurmann
Copy link
Author

@jerameel that's the case i'm referring, close the app and remove it from "recent apps", or android multitasking.

@stale stale bot removed the Stale There has been a lack of activity on this issue and it may be closed soon. label Feb 20, 2018
@react-native-bot
Copy link
Collaborator

Thanks for posting this! It looks like you may not be using the latest version of React Native, v0.53.0, released on January 2018. Can you make sure this issue can still be reproduced in the latest version?

I am going to close this, but please feel free to open a new issue if you are able to confirm that this is still a problem in v0.53.0 or newer.

How to ContributeWhat to Expect from Maintainers

@react-native-bot react-native-bot added Ran Commands One of our bots successfully processed a command. Stale There has been a lack of activity on this issue and it may be closed soon. labels Feb 24, 2018
@stale stale bot removed the Stale There has been a lack of activity on this issue and it may be closed soon. label Feb 24, 2018
@facebook facebook locked as resolved and limited conversation to collaborators Feb 24, 2019
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Feb 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

3 participants