You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which is executed on boot of the app and after a reload. It works fine without Expo. With Expo however, self.bridge.surfacePresenter is correct on boot and nil after a reload.
After a reload the setter here
doesn't get called for the bridge acquired by Reanimated. This causes the app to crash. Keep in mind you don't need to use Reanimated, only have it installed.
It might be related to the fact that
is only executed on boot, but I'm not sure about that.
Hi @tjzel I believe this is actually a race condition happening while the bridge is being invalidated, I can reproduce this same issue in a project without expo by reloading the app by double pressing "r"
This issue was closed because it has been inactive for 7 days since being marked as stale. Please open a new issue if you believe you are encountering a related problem.
Summary
This issue was reported to Reanimated: software-mansion/react-native-reanimated#5497.
In Reanimated we have the following line:
Which is executed on boot of the app and after a reload. It works fine without Expo. With Expo however,
self.bridge.surfacePresenter
is correct on boot andnil
after a reload.After a reload the setter here
doesn't get called for the bridge acquired by Reanimated. This causes the app to crash. Keep in mind you don't need to use Reanimated, only have it installed.
It might be related to the fact that
is only executed on boot, but I'm not sure about that.
Managed or bare workflow?
bare
What platform(s) does this occur on?
iOS
Package versions
Environment
Reproducible demo
Follow the reproduction steps provided here software-mansion/react-native-reanimated#5497.
Stacktrace (if a crash is involved)
No response
The text was updated successfully, but these errors were encountered: