-
Notifications
You must be signed in to change notification settings - Fork 94
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
Error: getRectForRef - current is not set (Unhandled Promise Rejection) iOS #153
Comments
Not sure if it's related, but I'm getting that same error "getRectForRef" on android when handling popover visibility through state rather than ref. |
Try setting the useNativeDriver to false for the animations and see if it changes anything.
|
I'm seeing this behavior too, when I conditionally render a Popover, as opposed to just using |
Unfortunately still facing the warning with this config |
same issue, is there any working fix/workaround? |
Using Patch Package I was able to get it working.
To get it running on production builds properly I also needed to add: |
Also seeing this clogging up my error reporting. It doesn't seem to be causing any problems but it is causing thousands of error reports to come in. |
You guys found any solution to this problem? |
I encountered this warning when the source component was removed from the hierarchy. I found that making the source component a forwardRef fixed it for me.
...
[Edit] This appeared to fix the issue this morning, but now the warning is back. Not a fix. |
Facing the same problem on a menu option to delete a item: when deleted, the item is removed from it's parent and with it the whole popover. So it gives me the warning. If I wait like 2 seconds it doesn't warn. |
Also experiencing this on web. When it happens on the web it locks up the entire app until reloaded. |
I'm facing the exact same issue, any update on a fix ? |
it seems this isn't maintained at all. this error is coming in a lot for me as well... |
Describe the bug
'Error: getRectForRef - current is not set' is being thrown when a replace (replace, native back navigation) navigation (native-stack) is being triggered from popover.
Behaves slightly differently when built with or without hermes:
With Hermes:
Or just:
Without Hermes:
Causes screen freezes and crashes on big busy ipad app.
I am happy to have a dig at finding a solution and creating a PR but I will need input on how to resolve the issue.
I have not tested on Android.
Device/Setup Info:
**Debug Output**
Minimal Reproducable Example
Run ios and then notice the error when navigation from screen 2 to screen 1 - using navigation.navigate removes screen 2 from the stack and navigates to screen 1
Possibly Connected to:
Issue 145
Issue 69
The text was updated successfully, but these errors were encountered: