You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like get some input on the idea of default Android back button behavior for navigation when it's the last activity on a stack.
The current implementation is to kill the activity and causes a much longer time to start the app next time. I'm proposing to only minimizing the app as an alternative.
Back button should kill the activity if there's nothing to pop. The issue which you've linked to proposes a solution to the problem, as it will greatly speed up launch time. We use it in the Wix app with great success, and that's the default behaviour in v2.
Alternatively, you can override the back button in your root screen by setting overrideBackPress: true in tab declaration .
Then, listen to backPress navigation event in the root screens and programatically send the app to the background (you'll need to do some native work here I think, starting the launcher intent is one way of achieving this)
regardless, overriding back handling isn't something RNN should be responsible so I'm opting to close the issue.
Best of luck
Hello everyone,
I'd like get some input on the idea of default Android back button behavior for navigation when it's the last activity on a stack.
The current implementation is to kill the activity and causes a much longer time to start the app next time. I'm proposing to only minimizing the app as an alternative.
Issue Description
I got inspired by this comment.
#1022 (comment)
Steps to Reproduce / Code Snippets / Screenshots
Environment
The text was updated successfully, but these errors were encountered: