Skip to content

Commit 09e0600

Browse files
fix(ci): Android merges stop cutting a new Play Store build every time
The production workflow's Android fingerprint never included the Google services file that EAS build servers hash, so no build ever matched and each merge to main rebuilt and submitted Android instead of publishing an OTA. Export the pulled file path the way the preview workflow already does. Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent 612a8e5 commit 09e0600

1 file changed

Lines changed: 14 additions & 1 deletion

File tree

‎.github/workflows/mobile-eas-production.yml‎

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -160,7 +160,20 @@ jobs:
160160
working-directory: apps/mobile
161161
env:
162162
EXPO_TOKEN: ${{ secrets.EXPO_TOKEN }}
163-
run: eas env:pull production --non-interactive
163+
run: |
164+
eas env:pull production --non-interactive
165+
# EAS commands skip dotenv, and the Android fingerprint hashes this
166+
# file. Without it every merge misses the build's hash and rebuilds.
167+
node --input-type=module <<'NODE'
168+
import { appendFileSync, readFileSync } from "node:fs";
169+
import { parseEnv } from "node:util";
170+
const env = parseEnv(readFileSync(".env.local", "utf8"));
171+
const googleServicesFile = env.T3CODE_ANDROID_GOOGLE_SERVICES_FILE;
172+
if (!googleServicesFile) {
173+
throw new Error("T3CODE_ANDROID_GOOGLE_SERVICES_FILE is missing from the production environment");
174+
}
175+
appendFileSync(process.env.GITHUB_ENV, `T3CODE_ANDROID_GOOGLE_SERVICES_FILE=${googleServicesFile}\n`);
176+
NODE
164177
165178
- name: Apply manual version override
166179
if: steps.version_app_token.outcome == 'success'

0 commit comments

Comments
 (0)