Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(iOS, Fabric): wrong headerCenter layout after native dismissal (#…
…2263) ## Description This PR fixes #2232 by disabling view recycling in `RNSScreenStackHeaderSubview` view component, as no better solution was found. The following sequence leads to the bug: 1. User clicks back button 2. The header subviews are properly removed and put in recycle pool in the same order they were mounted (recycle pool is a stack). 3. User pushes again just-popped-screen. 4. React Native reuses view from recycle pool, but `headerCenter` is to be mounted first, so RN reuses the view that was previously `headerRight` (because it is on top of the recycle pool stack). Similarly the second view in recycle pool, which was previously `headerCenter` is now repurposed as `headerRight`. 5. RN sets correct frames for both subviews. 6. System sets wrong frame for the new `headerCenter` due to layout triggered by `setNavigationBarHidden` in `updateViewController` of `RNSScreenStackHeaderConfig`. The `setNavigationBarHidden` is called, because there is difference in value of the prop between the screens (see issue for repro). The only fact that matters is the one, that native layout is triggered & it computes the `width` incorrectly <- it looks like UIKit does hold some cache for layout computations & when seeing the recycled view it just bonks it with it's previous frame, for some reason not observing that deeper in view hierarchy contents have changed. I've tried to invalidate layout of the subview in various places that could make sense, e.g. `prepareForRecycle`, just before computing native layout in `updateViewController`, etc. for no result. To avoid putting more debugging hours into this particular issue I went with disabling view recycling for header subviews, originally suggested by @janicduplessis in the issue description. ### Open questions We would want to answer those at some time in the future: 1. [ ] What's the difference between JS-initiated dismissal and native one, in this very case? Where does the difference in behaviour come from? (JS-initiated works properly) 2. [ ] In what other way can we solve this w/o disabling view recycling? Fixes #2232 ## Changes Disable view recycling in `RNSScreenStackHeaderSubview` view component. ## Test code and steps to reproduce `Test2232` ## Checklist - [x] Included code example that can be used to test this change - [x] Ensured that CI passes
- Loading branch information