IOS Not full animation to the pressed tab when keyboard is opened

[Kruglyanski]

Current behavior

Animation between tabs not scrolls to the end. The onIndexChange not fires as a result. Animation ends if click on content

https://user-images.githubusercontent.com/45219732/182527044-70fa1bcb-52dd-46fb-9c66-c23b91732553.mp4

Expected behavior

Animation ends, onIndexChange fires

Reproduction

Platform

• [ ] Android
• [X] iOS
• [ ] Web
• [ ] Windows
• [ ] MacOS

Environment

package	version
react-native-tab-view	3.1.1
react-native-pager-view	5.4.25
react-native	0.64.2
expo	no
node	18.7.0
npm or yarn	npm 8.15.0

[github-actions[bot]]

Hey! Thanks for opening the issue. The issue doesn't seem to contain a link to a repro (a snack.expo.dev link or link to a GitHub repo under your username).

Can you provide a minimal repro which demonstrates the issue? A repro will help us debug the issue faster. Please try to keep the repro as small as possible and make sure that we can run it without additional setup.

[github-actions[bot]]

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

• expo

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

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

• react-native (found: 0.64.2, latest: 0.69.3)

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

[steffenabel]

I'm experiencing the same issue with version 3.1.1 and the current RN version (0.69.1) when using a textinput with autofocus enabled. A downgrade to version 2.16.0 fixes the issue.

[okwasniewski]

Hey @Kruglyanski can you add a snack reproducing this?

[github-actions[bot]]

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.