EAS Update not detecting secrets about eas-cli HOT 3 CLOSED

Hi there!

Sorry for making it confusing, but secrets are only used when doing your EAS cloud builds at the moment. The eas update command uses env vars available in your local environment and doesn't have access to secrets stored on EAS servers. Here are the docs about how you can use env variables when using EAS Update: https://docs.expo.dev/eas-update/environment-variables/.

With that being said, we have some plans to improve the situation regarding env vars this year to make it easier to work with/less confusing. I think that if you are waiting for this it would be best if you follow our changelog to stay up to date with all EAS changes 🙂

I'm going to close the issue because it technically is not a bug, but a way this functionality works at the moment. Please, let me know if you have any more questions!

from eas-cli.

@szdziedzic
If that is the case. We are back to .env is not being loaded on eas update problem

I have .env file. it is working without problem on expo dev.

But when i use expo update

from eas-cli.

Again issue is closed. I am creating new one.

#2174

from eas-cli.