Closed julian-gargicevich closed 1 year ago
Hi @julian-gargicevich, we are working on it.
Thanks for the quick reply @brunokiafuka
Docs say it was tested with expo 48? Which version? I'm happy to downgrade in order to get it to work until you fix the issue
We have test with expo 48 and watermelonDB v0.25.5
Hi @julian-gargicevich can you install "@morrowdigital/watermelondb-expo-plugin": "^2.1.1"
and re-run the npx expo run:[ios | android]
. This new version aims to fix "@nozbe/watermelondb": "^0.26.0"
, please make sure that you have it on the lates version.
Feel free to reopen the issue if this persists. Thanks :)
Getting the same error when running eas build
to build the dev client :(
If you managed to successfully generate custom dev-client, and the issue only when running eas build
this might be related to eas cache, so you can maybe try disable it and re-run the build.
https://docs.expo.dev/build-reference/caching/#javascript-dependencies
Let me know if this works.
eas build
is used to generate the dev client, tried flushing everythig cache related and still getting the same error. I'll try with a new project to see if it's related to my project but it doesn't look like it? Saw someone else was getting a similar error with the non-modular headers
I'm getting this error when trying to build the custom dev client
My plugins in app.json looks like this:
I'm using: