leons1767

`eas update` does not have access to SECRETS variables or environment variables that you defined in eas.json. You can use `dotenv` to export the `.env` variables locally to `eas update`....

> @leons1767 let's say that I am maintaining the correct SERVER value in the .env file, can you explain why `eas update` changes the value intermittently? I don't think it...

> I deleted a previous comment, because I found the [relevant documentation](https://docs.expo.dev/eas-update/environment-variables/#sharing-environment-variables-between-local-development-eas-update-and-eas-build:~:text=Your%20local%20development,eas.json.) for this issue Glad that you are able to find the answer from the documentation. Have a nice...

Hello @fateh999 , May I know if you have abandon this project? The issue mentioned here in been fixed by @KeaganStevens for a while, and waiting to be merged. This...

Thanks @AidanWelch I only sent 2 identical sentences in the array, to translate to different languages. I guess I will need a retry bloc.

> I was able to solve it via app.json. Add under plugins `expo-build-properties`: > > ``` > [ > "expo-build-properties", > { > "android": { > "extraMavenRepos": [ > "../../node_modules/react-native-adapty/lib/android/localMaven"...