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
Describe the bug
The updates @michaelessiet made in the package are cool and all, but the newly added lock files from #10 are messing up the initial android build.
I had to remove them both (Yarn.lock & package-lock.json) and reinstall the dependencies (using yarn command, surely) with a new autogenerated yarn-lock file in order to get the project to run (on android 🤖).
After that the yarn android command worked flawlessly.
With the files offered by @michaelessiet it was giving me the error below.
To Reproduce
Steps to reproduce the behavior:
Clone the repo
Try to run the app: yarn && yarn android
After bundling is complete, see the error:
ERROR TypeError: _reactNativeReanimated.Easing.bezier(0.16, 1, 0.3, 1) is not a function. (In '_reactNativeReanimated.Easing.bezier(0.16, 1, 0.3, 1)(progress.value)', '_reactNativeReanimated.Easing.bezier(0.16, 1, 0.3, 1)' is
an instance of Object)
This error is located at:
in AnimatedCheckbox (created by TaskItem)
in RCTView (created by View)
in View (created by Pressable)
Expected behavior
No error 🐛
Screenshots
Desktop (please complete the following information):
OS: [Windows 10]
Smartphone (please complete the following information):
Device: [Android Emulator]
OS: [Android 11]
Additional context #7 could be related, so dear @kokosky93, if you're still confused by the error you received, maybe try deleting the lock files, then run yarn or npm i. It could help. :)
The text was updated successfully, but these errors were encountered:
neugomonov
added a commit
to neugomonov/react-native-animated-todo
that referenced
this issue
Jan 6, 2023
Describe the bug
The updates @michaelessiet made in the package are cool and all, but the newly added lock files from #10 are messing up the initial android build.
I had to remove them both (Yarn.lock & package-lock.json) and reinstall the dependencies (using
yarn
command, surely) with a new autogenerated yarn-lock file in order to get the project to run (on android 🤖).After that the
yarn android
command worked flawlessly.With the files offered by @michaelessiet it was giving me the error below.
To Reproduce
Steps to reproduce the behavior:
yarn && yarn android
Expected behavior
No error 🐛
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
#7 could be related, so dear @kokosky93, if you're still confused by the error you received, maybe try deleting the lock files, then run
yarn
ornpm i
. It could help. :)The text was updated successfully, but these errors were encountered: