-
-
Notifications
You must be signed in to change notification settings - Fork 545
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to find parent screen controller #2717
Comments
Hey! 👋 The issue doesn't seem to contain a minimal reproduction. Could you provide a snack or a link to a GitHub repository under your username that reproduces the problem? |
I faced the same issue. After hours of debugging, I discovered that the error occurs when using |
Yeah also getting the same error on navigation.reset. I just did a quick check with the new architecture to confirm and it indeed stopped the crashing. Although annoyingly i can't do the migration as currently there are too many other issues around the new architecture for my project.... |
I resolved this issue by downgrading the navigation and screen packages while using React Native 0.74.2. The versions I used are:
|
same here
|
I'm working on it. I'll release a patch in ~1h |
… content wrapper (#2719) ## Description Closes #2717 For some reason on old architecture, when calling `navigation.replace()` the replaced screen receives `willMoveToWindow:` message from UIKit with non-nil argument, defying my previous expectations. On new architecture this works as expected: removed screen receives `nil` window & we do not run the content-wrapper-attachment logic. ## Changes Error is logged only on new architecture now. ## Test code and steps to reproduce WIP ## Checklist - [x] Included code example that can be used to test this change - [ ] Ensured that CI passes
@kkafar I'm also seeing this problem after upgrading to 4.8.0. Do you know roughly when a patch will be released? 🙏 |
I hope to have stable 4.9.0 released today. But I guess I can release another beta in 20 minutes. BUT please note that 4.9.0-beta.x requires 0.78 react-native version. |
@steinalex 4.9.0-beta.1 is available on npm |
Thanks for the update @kkafar. Just to confirm, will the non-beta release (4.9.0) also require |
@kkafar @steinalex same question here |
@steinalex I'm not sure how the backward compatibility will look like yet. I'm working on bringing it in this very moment. |
@kkafar Will it be mandatory for 4.9.0 to have react native version >=0.78.0? as upgrading to 0.78 is not possible in my case as we are working on 0.76.7, by disabling the new arch, and we are concurrently solving the layout issues because of migrating to new arch |
From what I understand, Expo 52 (latest SDK) doesn't support React Native higher than 0.76: https://github.com/expo/expo/blob/sdk-52/package.json#L22. I think Expo 52 users (myself included) will be stuck on this issue unless it's supported on older RN versions |
It does support https://expo.dev/changelog/2025-01-21-react-native-0.77 |
I've just released 4.9.0. Old architecture should work from 0.76 onward & new architecture should work from 0.77 onward. |
Description
Hi,
After upgrading from 4.6.0 to 4.7.0 or 4.8.0 I am getting the below error attached. I am on old arch.
Steps to reproduce
Snack or a link to a repository
https://picture.attached.com
Screens version
4.7.0 or 4.8.0
React Native version
0.77.1
Platforms
iOS
JavaScript runtime
Hermes
Workflow
React Native (without Expo)
Architecture
Paper (Old Architecture)
Build type
Debug mode
Device
Real device
Device model
iPhone 16 Pro Max
Acknowledgements
Yes
The text was updated successfully, but these errors were encountered: