fix(android): Corrected TabView fragment manager resolution#11217
Conversation
|
View your CI Pipeline Execution ↗ for commit 5b9d9ee
☁️ Nx Cloud last updated this comment at |
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughAndroid TabView fragment manager resolution is simplified: ChangesTabView Fragment Manager Resolution
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
PR Checklist
What is the current behavior?
Right now, there's an issue that causes android TabView tabs to become blank if users switches tabs quickly.
This triggers a chain of events:
_getChildFragmentManageroverridden method returns the wrong fragment manager because the previous fragment wasn't detached from fragment manager during tab navigationFragmentManager.What is the new behavior?
This PR will remove the faulty child fragment resolution code since it has no merits but causes problems instead.
Partially reverts #6293 which seems to be the culprit.
Fixes #10165.
Note: We can consider a huge refactor for TabView in the future and see if it's possible to use ViewPager2 or FragmentStatePagerAdapter