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
Hi Ragnar Rebase (@rrebase), what version of react-native are you using? Are you building with new arch enabled? Do you have a minimal repro I can have a look at? I don't think I've seen this issue before.
I'm not sure what's going on though. But it doesn't seem like it's an issue with react-native-test-app in particular. It seems like installTurboModule() is making some assumptions that isn't always true.
Update: I had a closer look at how installTurboModule() works and it's quite… hacky, to say the least. This is not a reliable way to install a custom runtime at all, and it's basically polluting all classes inheriting from UIResponder. Since it is a fairly popular package, I think we will have to support it somehow if upstream can't come up with a better solution. Definitely not like this though.
I put up a PR with a proposal for a fix. It leverages config plugins to install the Reanimated runtime. I still need to do more testing, but would love to hear your feedback on it.
Activity
[-]Unable to install reanimated[/-][+]iOS: Unable to install reanimated[/+]tido64 commentedon Nov 7, 2022
Hi Ragnar Rebase (@rrebase), what version of react-native are you using? Are you building with new arch enabled? Do you have a minimal repro I can have a look at? I don't think I've seen this issue before.
rrebase commentedon Nov 7, 2022
RN versions 0.68.2 & 0.70.0. I'll prepare a minimal repro 🙂
rrebase commentedon Nov 7, 2022
Minimal repro https://github.com/rrebase/react-native-test-app/tree/reanimated-demo
tido64 commentedon Nov 7, 2022
Ragnar Rebase (@rrebase): I managed to repro it. I also found this issue: software-mansion/react-native-reanimated#3420
There's a workaround posted here: software-mansion/react-native-reanimated#2791 (comment)
I tried it and it seems to be working:
I'm not sure what's going on though. But it doesn't seem like it's an issue with react-native-test-app in particular. It seems like
installTurboModule()is making some assumptions that isn't always true.Update: I had a closer look at how
installTurboModule()works and it's quite… hacky, to say the least. This is not a reliable way to install a custom runtime at all, and it's basically polluting all classes inheriting fromUIResponder. Since it is a fairly popular package, I think we will have to support it somehow if upstream can't come up with a better solution. Definitely not like this though.tido64 commentedon Nov 10, 2022
I put up a PR with a proposal for a fix. It leverages config plugins to install the Reanimated runtime. I still need to do more testing, but would love to hear your feedback on it.