Couldn't find version numbers for the following packages in the issue:

• @react-navigation/native
• @react-navigation/material-top-tabs

Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3.

Current Behavior We are using @react-navigation/material-top-tabs library to build carousal navigation which have 6 screens. We are using video player in one of screens where we have the functionality to make the video full screen.

When we click on the full screen button, we are seeing the cut screen of top tab menu screen. it shows half part of two screens, connected for a fraction of second before loading the landscape mode. This issue is very sporadic.

Expected Behavior it should have a smooth transition from portrait to landscape and vice versa.

How to reproduce

1. Create material top tab bar with multiple screens
2. try to switch between portrait to landscape.

Your Environment Issue occurring on both IOS and Android

@satya164 sorry, I really don't remember exactly how this is related in my case. But I already have a workaround. I will open a new issue if I remember in the future.

@davidmoss looking at that commit, it would only add a warning that the navigation is not yet initialized?

I will double check which version I'm using and test again, but if it was only that commit you referenced I wouldn't say that's a fix - it's just printing out to console the issue we are already discussing in this thread. Thanks a lot for the effort here, I'm super grateful, just trying to find a way to make navigating when opening a cold app from a deep link / notification work consistently.

Updating to the latest @react-navigation/native fixes this since 5.8.6: https://github.com/react-navigation/react-navigation/commit/4c2379cec1e661aa132002fd1c50909ea64cb983

@satya164 I need to track open progress animation state

Do you have react-native-screens enabled in your project (i.e. calling enableScreens())? Can you remove it for iOS and see if fixes the issue? (or specify detachInactiveScreens to false https://reactnavigation.org/docs/stack-navigator#detachinactivescreens)

detachInactiveScreens to false solves the problem though what was the cause?

I want to log every route change, and I tried quite some stuff but I always get this warning too, but I can't use getFocusedRouteNameFromRoute with the navigator ref, how can I manage ?

class App extends React.Component {

  onStateChange = async () => {
    if (!this.navigationRef) return;
    const currentRouteName = this.navigationRef.getCurrentRoute().name;
    if (currentRouteName === this.prevCurrentRouteName) return;
    this.prevCurrentRouteName = currentRouteName;
    console.log({ currentRouteName })
  };

  render() {
    return (
        <NavigationContainer
          ref={(r) => (this.navigationRef = r)}
          onStateChange={this.onStateChange}>
            {this.props.children}
        </NavigationContainer>
    );
  }
}

My app was stuttering because of this and I decided to follow a tutorial on youtube and create it myself. It's not the same thing but quite similar.

https://www.youtube.com/watch?v=ZiSN9uik6OY Thanks for the solution, I used another tab component instead, and I will check the tutorial as well, thank you ~

Deploy preview for react-navigation-docs ready!

Built with commit affe3875b5a850e91a0d9da47740540ddf905db5

https://deploy-preview-897--react-navigation-docs.netlify.app

The hyperlinks were pointing to the archived react-navigation repo so updated them to active repo and that particular branch file.

@Mavenic have you resolve this issue?

Codecov Report

Merging #9099 (e58f5eb) into main (1406eb8) will decrease coverage by 0.04%. The diff coverage is 37.50%.

@@            Coverage Diff             @@
##             main    #9099      +/-   ##
==========================================
- Coverage   72.90%   72.85%   -0.05%     
==========================================
  Files         135      135              
  Lines        3454     3459       +5     
  Branches     1088     1067      -21     
==========================================
+ Hits         2518     2520       +2     
  Misses        827      827              
- Partials      109      112       +3     

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 1406eb8...e58f5eb. Read the comment docs.

Deploy preview for react-navigation-example ready!

Built with commit 9e9dcddefe245faae059342c40dd4f54b885ed60

https://deploy-preview-9099--react-navigation-example.netlify.app

I have opened an issue earlier today that describes the problem: #9098

I think, I have found the problem and created a pull request #9099.

openByDefault in connection with expo-links only works for getInitialState(). When a page of the application is refreshed, getRehydratedState() is called and the drawer stays closed. This should fix the issue.

keep happening:

"@react-navigation/drawer": "^5.11.4", "@react-navigation/native": "^5.8.10", "@react-navigation/stack": "^5.12.8",

Hi Satyajit, thanks for your reply. I am not using it directly. I had to downgrade the lib to get nested nav to work.

On Nov 24, 2020, at 7:10 AM, Satyajit Sahoo [email protected] wrote:  You shouldn't be using @react-navigation/core directly.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

Current Behavior With routes defined (expo-linking and passed to NavigationContainer as linking-prop, the drawer does not open initially on any route other than / on the web, even though openByDefault is set to true on Drawer.Navigator. This applies to all drawerTypes other than permanent.

<NavigationContainer linking={linking}>
    <Drawer.Navigator openByDefault={true}>
        ...
    </Drawer.Navigator>
</NavigationContainer>

Expected Behavior The drawer should open by default when I refresh the page on /my/route. Currently the drawer only opens on /.

How to reproduce Define any linking object, set openByDefault to true and refresh the application on any route other than /.

Your Environment

Ok, that's interesting... I had no empty route defined in my linking object because I wanted every route to have a name. I didn't think that this was impossible.

This works

const linking = {
    prefixes: [prefix],
    config: {
        screens: {
            Welcome: "",
            PersonalInformation: "personal-information",
            Payments: "payments",
            Subscriptions: "subscriptions",
        },
    },
};

while this doesn't

const linking = {
    prefixes: [prefix],
    config: {
        screens: {
            Welcome: "welcome",
            PersonalInformation: "personal-information",
            Payments: "payments",
            Subscriptions: "subscriptions",
        },
    },
};