Error Initializing Prisma on Expo
I've created an Expo project which I am trying to connect to Supabase via Prisma, but I get the following error after bundling on my physical device:
I'm sure this is the result of some small mistake in configuration, but I've looked for answers eleswhere and haven't found any similar issues. I tried clearing the cache with
Happy to provide more details if needed.
ERROR Error: 🟥 @prisma/react-native failed to initialize, js engine: hermes
at ContextNavigator (http://10.0.0.213:8081/node_modules%5Cexpo-router%5Centry.bundle//&platform=ios&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=app:144849:24)
at ExpoRoot (http://10.0.0.213:8081/node_modules%5Cexpo-router%5Centry.bundle//&platform=ios&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=app:144805:28)
at App
at ErrorToastContainer (http://10.0.0.213:8081/node_modules%5Cexpo-router%5Centry.bundle//&platform=ios&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=app:429756:24)
at ErrorOverlay
at withDevTools(ErrorOverlay) (http://10.0.0.213:8081/node_modules%5Cexpo-router%5Centry.bundle//&platform=ios&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=app:429259:27)
at RCTView
at View (http://10.0.0.213:8081/node_modules%5Cexpo-router%5Centry.bundle//&platform=ios&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=app:40763:43)
at RCTView
at View (http://10.0.0.213:8081/node_modules%5Cexpo-router%5Centry.bundle//&platform=ios&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=app:40763:43)
... (etc)ERROR Error: 🟥 @prisma/react-native failed to initialize, js engine: hermes
at ContextNavigator (http://10.0.0.213:8081/node_modules%5Cexpo-router%5Centry.bundle//&platform=ios&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=app:144849:24)
at ExpoRoot (http://10.0.0.213:8081/node_modules%5Cexpo-router%5Centry.bundle//&platform=ios&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=app:144805:28)
at App
at ErrorToastContainer (http://10.0.0.213:8081/node_modules%5Cexpo-router%5Centry.bundle//&platform=ios&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=app:429756:24)
at ErrorOverlay
at withDevTools(ErrorOverlay) (http://10.0.0.213:8081/node_modules%5Cexpo-router%5Centry.bundle//&platform=ios&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=app:429259:27)
at RCTView
at View (http://10.0.0.213:8081/node_modules%5Cexpo-router%5Centry.bundle//&platform=ios&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=app:40763:43)
at RCTView
at View (http://10.0.0.213:8081/node_modules%5Cexpo-router%5Centry.bundle//&platform=ios&dev=true&hot=false&lazy=true&transform.engine=hermes&transform.bytecode=true&transform.routerRoot=app:40763:43)
... (etc)I'm sure this is the result of some small mistake in configuration, but I've looked for answers eleswhere and haven't found any similar issues. I tried clearing the cache with
npx expo start --clearnpx expo start --clearHappy to provide more details if needed.
