react-native-navigation icon indicating copy to clipboard operation
react-native-navigation copied to clipboard

bottomTabs+topBar with drawBehind/visible=true not working when pushing a screen with animation options

Open thanksyouall opened this issue 2 years ago • 1 comments

🐛 Bug Report

If I use the option for animations and also set drawBehind=true (or visible=false) for bottomTabs and topBar, the application does not respond.

Have you read the Contributing Guidelines on issues?

Yes

To Reproduce

  1. Clone my repo – https://github.com/thanksyouall/wix-nav-bug
  2. Run: yarn;
  3. Run: yarn start;
  4. Run: run from Xcode or yarn ios;
  5. Click on "Push Settings Screen".

Expected behavior

I expect to move to the next screen with this options: https://github.com/thanksyouall/wix-nav-bug/blob/main/index.js#L77-L87

Actual Behavior

The app stops responding, push to the next screen does not work.

Your Environment

  • React Native Navigation version: ^7.30.0-alpha (it doesn't work on previous versions either)
  • React Native version: 0.69.4
  • Platform(s) (iOS, Android, or both?): iOS
  • Device info (Simulator/Device? OS version? Debug/Release?): Simulator, Ipad Prop 11-inch, debug.

Reproducible Demo

https://github.com/thanksyouall/wix-nav-bug

thanksyouall avatar Aug 17 '22 18:08 thanksyouall

Up

thanksyouall avatar Sep 18 '22 09:09 thanksyouall

UP UP UP

thanksyouall avatar Oct 28 '22 09:10 thanksyouall

Hey there, I've never replied on github before but maybe this will help you. Here's an example of my navigation push code. I push my options inside of the push itself, hope it helps!

Navigation.push(this.props.componentId, {
      component: {
        name: 'account',
        passProps: {
        },
        options: {
          topBar: {
            title: {
              text: "Account",
            },
          },
          bottomTabs: {
            visible: false,
            drawBehind: true
          }
        }
      }
    });

goldfish15 avatar Nov 06 '22 21:11 goldfish15

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe the issue is still relevant, please test on the latest version and report back. Thank you for your contributions.

stale[bot] avatar Feb 19 '23 10:02 stale[bot]

The issue has been closed for inactivity.

stale[bot] avatar Mar 14 '23 12:03 stale[bot]