-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
Building Expo App locally Fails: envs are not defined in local build process. #487
Comments
Hey, thank you for opening this issue! 🙂 To boost priority on this issue and support open source please tip the team at https://issuehunt.io/r/goatandsheep/react-native-dotenv/issues/487 |
Reinstall as devDependency |
added new images. Is this relevant: https://docs.expo.dev/guides/environment-variables/#how-to-read-from-environment-variables |
@AyoCodess unfortunately no it's not particularly relevant. It's a separate way of loading environment variables that works quite well. You may be able to use that method instead of this library altogether. I haven't tried it out myself though so if you do, please let me know! Thank you for confirming it's a devDependency. I'll check it off in your issue description. Do you have a env.d.ts file? If you have an example repo of this not working it helps me tremendously as I can pinpoint exactly where the issue may be :) |
I'll create one. |
any solution? i'm facing the same problem, i've tried everything, no success. |
Describe the bug
envs are not defined in local build process.
To Reproduce
Steps to reproduce the behavior:
local builds
Expected behavior
env should be loaded into build process
Screenshots
edit: (IM USING EXPO_PUBLIC_)
Desktop (please complete the following information):
Mac book pro
Additional context
My app picks up the envs while developing just fine. it only failed when i build the app.
am i missing something in my set up?
works as expected during development.
import { EXPO_PUBLIC_CONVEX_URL, EXPO_PUBLIC_CLERK_PUBLISHABLE_KEY } from "@env";
The text was updated successfully, but these errors were encountered: