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

In Android 14, app gets restarted when navigating from portrait to landscape screen #11845

Closed
3 of 11 tasks
kunjalsoni-simformsolutions opened this issue Feb 23, 2024 · 3 comments

Comments

@kunjalsoni-simformsolutions
Copy link

Current behavior

I have 2 screens in my stack navigator, A and B.
For A, I haven't specified any orientation, but for screen B, I have provided landscape orientation.
When I navigate from portrait screen screen A to landscape screen B, the app gets restarted from its entry point, making it impossible to navigate to screen B.
There are no error logs shown in the console.

Expected behavior

Stack navigator should allow navigating from portrait screen A to landscape screen B without any issues.

Reproduction

https://github.com/react-navigation/react-navigation

Platform

  • Android
  • iOS
  • Web
  • Windows
  • MacOS

Packages

  • @react-navigation/bottom-tabs
  • @react-navigation/drawer
  • @react-navigation/material-top-tabs
  • @react-navigation/stack
  • @react-navigation/native-stack
  • react-native-tab-view

Environment

  • [] I've removed the packages that I don't use
package version
@react-navigation/native 6.1.10
@react-navigation/drawer 6.6.7
@react-navigation/stack 6.3.21
@react-navigation/native-stack 6.9.18
react-native-screens 3.9.0
react-native-gesture-handler 1.10.3
react-native-reanimated 2.2.4
react-native-tab-view 2.16.0
react-native-pager-view 5.4.9
react-native 0.66.5
node 16.16.0
yarn 1.22.19
Copy link

Hey @kunjalsoni-simformsolutions! Thanks for opening the issue. It seems that the issue doesn't contain a link to a repro.

The best way to get attention to your issue is to provide an easy way for a developer to reproduce the issue.

You can provide a repro using any of the following:

A snack link is preferred since it's the easiest way to both create and share a repro. If it's not possible to create a repro using a snack, link to a GitHub repo under your username is a good alternative. Don't link to a branch or specific file etc. as it won't be detected.

Try to keep the repro as small as possible by narrowing down the minimal amount of code needed to reproduce the issue. Don't link to your entire project or a project containing code unrelated to the issue. See "How to create a Minimal, Reproducible Example" for more information.

You can edit your original issue to include a link to the repro, or leave it as a comment. The issue will be closed automatically after a while if you don't provide a repro.

Copy link

The versions mentioned in the issue for the following packages differ from the latest versions on npm:

  • react-native-tab-view (found: 2.16.0, latest: 3.5.2)

Can you verify that the issue still exists after upgrading to the latest versions of these packages?

Copy link

Hello 👋, this issue has been open for more than a month without a repro or any activity. If the issue is still present in the latest version, please provide a repro or leave a comment within 7 days to keep it open, otherwise it will be closed automatically. If you found a solution or workaround for the issue, please comment here for others to find. If this issue is critical for you, please consider sending a pull request to fix it.

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

No branches or pull requests

1 participant