Closed thaindangelhack closed 3 days ago
Hey @thaindangelhack! 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:
GitHub repo under your username
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.
Couldn't find version numbers for the following packages in the issue:
@react-navigation/bottom-tabs
@react-navigation/drawer
@react-navigation/material-top-tabs
@react-navigation/stack
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-navigation/native
(found: 6.1.2
, latest: 6.1.18
)Can you verify that the issue still exists after upgrading to the latest versions of these packages?
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.
Current behavior
Details:
=> I found that only when I switch from the last tab to the first tab, it is not called, although in other tab switches, this function is called to the corresponding index.
Current evidence:
https://github.com/user-attachments/assets/f65a1c89-2947-4b29-946a-f492483cea0e
After set animationEnabled={false} in TabView
The error is gone, but the animation will not be usable. https://github.com/user-attachments/assets/be5b6008-3103-4731-a5e7-7e893691a517 Solution I find in that https://github.com/react-navigation/react-navigation/issues/11874#issuecomment-2035589010
Expected behavior
can fix the above error and still use animation
Reproduction
/
Platform
Packages
Environment