React-native-tab-view: the position of Indicator error when i navigate back from an lazy import view

Created on 6 Feb 2021  路  2Comments  路  Source: satya164/react-native-tab-view

Current behaviour

the position of Indicator error when i navigate back from an lazy import view, like this:
const AuthcodeManagerScreen = lazy( () => import('pages/mine/authcode/screen/AuthcodeManagerScreen'))

when i import like this:
import AuthcodeManagerScreen from 'pages/mine/authcode/screen/AuthcodeManagerScreen'

the problem is gone

only in android, iOS is correct

Expected behaviour

how can I fix this problem? lazy import is important for me , i do not want to give up

Code sample

      <Observer>
        {() => {
          return (
            <TabView
              navigationState={{ index: store.index, routes: store.routes }}
              renderScene={renderScene}
              onIndexChange={store.handleIndexChange}
              initialLayout={initialLayout}
              renderTabBar={renderTabBar}
              lazy
            />
          )
        }}
      </Observer>

Screenshots (if applicable)

What have you tried

i tried use renderIndicator and default Tabbar, still alive

Your Environment

| software | version
| ---------------------------- | -------
| ios or android | android
| react-native | 0.63.3
| react-native-tab-view | 2.15.2
| react-native-gesture-handler | 1.9.0
| react-native-reanimated | 1.13.2
| node | v10.15.3
| npm or yarn | yarn 1.22.5

bug

All 2 comments

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

  • react-native (found: 0.63.3, latest: 0.63.4)

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

@ryankask expect a reply

Was this page helpful?
0 / 5 - 0 ratings

Related issues

glennvgastel picture glennvgastel  路  3Comments

jouderianjr picture jouderianjr  路  3Comments

itzsaga picture itzsaga  路  3Comments

lubomyr picture lubomyr  路  3Comments

compojoom picture compojoom  路  4Comments