-
Notifications
You must be signed in to change notification settings - Fork 187
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
Update documentation for react-native-reanimated
and bump version in Example
#73
Comments
I'm facing this issue when trying to bump the version software-mansion/react-native-reanimated#1640 The workaround is to comment out the line responsible for the issue inside the node_modules. But wouldn't be able to deploy the preview from github actions. I would need to cancel all the actions and manually deploy, both for the main and for the PRs preview, which is really boring 🐤 |
@PedroBern I had to |
I tried all kind of reset cache, including the metro bundler, but I still have the issue. |
While trying to test #58 in an actual app I've also ran into this. None of the reanimated2 rc versions worked (0, 1 or 2). What did you do for a workaround @PedroBern? Commenting out the offending line is not something I can do in this project. |
@andreialecu I did nothing, kept the rc.0. I faced this issue only with rc.1 and rc.2. Are you using expo? here are some useful commands to clean all the cache I tried (just updated to yarn) without success. But you are not supposed to have this issue if not using expo. |
I'm not using expo, on
Which seems to be reported here: software-mansion/react-native-reanimated#1587 I cleared the caches using |
Oh, nevermind. After adding the babel plugin it works now (on rc.0, didn't try the others):
|
I had this issue too and right now I'm pretty confused on what I should to.
It should be mentioned somewhere UPDATE: SDK41 contains support for Reanimated 2 |
react-native-reanimated
v2 has quite a bit more set-up. It's not immediately clear that when installing the library, you have to be using v2 of the library.Also, things like Direct Debugging are things that people who install v2 may not be expecting.
Also, we should bump the version in the example to
2.0.0-rc.2
The text was updated successfully, but these errors were encountered: