# OTA update breaks Google sign-in (or changes the API URL) although the store build works

> EAS builds apply the env block of the eas.json build profile, but eas update does not.

Web page: https://davidewins.com/errors/eas-update-ignores-eas-json-env

Expo. Confirmed fix, 17 September 2026.

Versions: eas-cli eas update

There is no error message for this one, only the symptom in the title.

## Cause

EAS builds apply the `env` block of the eas.json build profile, but `eas update` does not. Local .env files can also leak into the update bundle. So the update can ship different values than the build it lands on.

## Fix

Keep every EXPO_PUBLIC_ value in one place (the EAS environment), or export the update with the same env the build used: move .env files aside, load `eas env:list production`, overlay the eas.json profile env, export with `--clear`, and grep the bundle for each value before publishing.

## More Expo errors

- [Dev client red screen: No script URL provided (launcher never appears)](https://davidewins.com/errors/expo-dev-client-no-script-url-precompiled)
- [Bundle fails with Invalid expression encountered after supabase-js update](https://davidewins.com/errors/supabase-js-hermes-invalid-expression)
- [After upgrading to SDK 57, expo-font / expo-image / expo-asset config is missing](https://davidewins.com/errors/expo-sdk57-plugins-must-be-declared)
- [SDK upgrade: export dies with SyntaxError after expo install --fix](https://davidewins.com/errors/expo-install-fix-leaves-babel-preset-stale)
- [expo-doctor wants TypeScript 6 but tsc reports hundreds of errors](https://davidewins.com/errors/typescript-6-explodes-typecheck-expo)

[Search all errors](https://davidewins.com/errors)