https://starter.obytes.com/getting-started/environment-vars-config/

[giscus[bot]]

https://starter.obytes.com/getting-started/environment-vars-config/

Environment variables and configuration with validation and type-checking.

https://starter.obytes.com/getting-started/environment-vars-config/

[chanphiromsok]

Env.NAME is undefined when use to build android

[yjose]

Yeah correct

[chanphiromsok]

now I write bashscript instead

[yjose]

I'm a bit curious about why you need to write a bash script instead of running pnpm run android🧐

[chanphiromsok]

I used to get error in android when running yarn android --variant=release in expo sdk49 that why I write bashscript

[rbshh]

While not the primary cause, it's worth checking if your .gitignore file unintentionally excludes the environment configuration files containing "Env.NAME". This can happen if you accidentally add patterns like .env or specific directory paths containing your environment files.

If this is the case, remove the relevant patterns from your .gitignore file to allow these files to be included during the build process. However, exercise caution and avoid committing sensitive information like API keys or passwords to your version control system.

[farrukhabbas]

I defined a number based env variable in the env.js, and assigned house: process.env.HOURS to the clientEnv object, then the pnpm ios fails with type error - cannot assign string to number, then when i convert the number like Number(process.env.HOURS) then the pre-commit fails with error cannot assign number to string, what can i do here? how to define a number variable ?

[yjose]

dotenv always reads env vars as strings, which is the normal behavior. the solution is exactly what you did but you need to some fixes on typing, check #296

[yjose]

For people trying to replicate the same approach in their own projects, a common issue we encounter

Unable to resolve module path means you are trying to import the path Node.js module into your app, which will not work because the runtime is different. This issue arises because you are importing the ./env.js file into a file located in the ./src folder, which Metro is attempting to bundle.

To resolve this, ensure you import your environment variables from @env, which should be an alias for ./src/core/env.js, instead of ./env.js.

[vlanemcev]

Hi, what do you think about new Expo Env handling model / approach?
It seems to be more convenient to use thanks to Expo's built-in capabilities.
Interesting to see your opinion, thank you!

https://expo.dev/blog/environment-variables

[yjose]

@vlanemcev thank you for bringing this up for discussion.

When Expo introduced automatic loading of environment variables, I tried to adapt the approach. Unfortunately, it did not work because they primarily support development and production only. As a we are uning staging too, I disabled their feature using EXPO_NO_DOTENV.

But now, as they introduce preview, which will be aligned with staging, I think we can adapt our approach to make it work smoothly with the new Expo approach. This should make it better and simpler for people to follow.

To be honest, I still haven't started working on it. I have some ideas, but feel free to share your thoughts on how we can adapt this to the new expo approach.