Dav

I would also like to see this fixed. Or at least add a buildNumber so that the devs can choose the one they care about

Thanks for your workaround @andrejpavlovic - however I found an issue which is preventing me from continuing, I load the dotenv config using the ES6 method: `import 'dotenv/config';` as described...

I have solved this issue for me anyway by utilising [`dotenvx`](https://github.com/dotenvx/dotenvx) which only injects the variables once and they persist no matter how many times `eas` calls the config function...

@AdamGerthel if you use npx then you don't need to install it as a project dependency, it will download it and use it on demand. eas.json is not very useful...

@olivierlesnicki This issue is fixed in version 0.73.4 - this issue should be closed.

I am also experiencing this issue and is very prominent on a "real world" app, I also assumed this has to do with the status bar but yet to have...

@techgerm Maybe something else is installing it as a dependency. Can you show us the output of the following command: ``` npm ls expo-status-bar ```

The error only happens in standalone build (not Expo Go) so I added a `yarn build` script to package.json. This should ask to setup a project in expo. You will...

> I fixed this error by changing the version of react-native-maps to 2.0.0-beta.14. > > The issue has been fixed in version [v.2.0.0-beta.10](https://github.com/react-native-maps/react-native-maps/releases/tag/v2.0.0-beta.10) I can confirm my app is working...

I agree, I would also raise an eyebrow if I saw a dependency on a beta. Yes ideally it would be fixed on react-native-maps, but they have been stable for...