-
Notifications
You must be signed in to change notification settings - Fork 9
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
Error: 🟥 @prisma/react-native failed to initialize #39
Comments
Related issue 23 is still open and has not been resolved. I use prisma for NextJS and it works flawlessly, sucks that this issue completely hard locks the package. |
I've got the same problem just for android, it's ok for ios but android throws this error |
you may have messed the order of commands |
@piscopancer i tried doing it but it didn't worked too i will get you the exact code(by making you collaborator for private repo) will you try to run and fix and tell me the problem |
I've tried everything and mine always gives the same error. `> Task :prisma_react-native:configureCMakeDebug[arm64-v8a] FAILED FAILURE: Build failed with an exception.
C++ build system [configure] failed while executing: CMake Error at CMakeLists.txt:10 (add_library): |
Ive just opened a new issue for this part, ive included a fix :) #47 |
I'm on the latest build as of September 28, 2024
I'm getting the Error:
Here are the steps I've taken and how I built the project:
Firstly, I've made the expo project:
Then I cd into the project and install the dependencies:
Then I connected the expo app to the expo go dashboard:
Then I run the app on the ios simulator:
Everything is good and works, so I go ahead and install prisma:
then I modify the app.json plugin section as follow:
Then I run the following:
Then I initialize prisma
Then I edit the schema with the following models:
Then I run a migration:
Then I generate prisma:
Then I make a db.ts file to use reactive queries:
Then I modify my component to use prisma:
Then I restart the app:
Then I get this error:
The text was updated successfully, but these errors were encountered: