userInterfaceStyle was hardcoded to "light" in app.json — since the app resolves its "Automatic" theme option via RN's useColorScheme(), which Expo only wires up to the OS when userInterfaceStyle is "automatic", the auto setting would have silently never followed the system theme in a real native build (only worked in the dev client, which isn't gated by this app.json field the same way). Also pin the preview/production EAS build profiles' EXPO_PUBLIC_* env vars explicitly in eas.json. .env is gitignored, so a cloud build has no guarantee of seeing it (or seeing the right values) — this makes the native build's API/Clerk/Supabase targets explicit and independent of whatever's in the local .env at build time. Values are non-secret (EXPO_PUBLIC_* is always inlined into the client bundle).
31 lines
789 B
JSON
31 lines
789 B
JSON
{
|
|
"cli": {
|
|
"version": ">= 23.2.0",
|
|
"appVersionSource": "local"
|
|
},
|
|
"build": {
|
|
"development": {
|
|
"developmentClient": true,
|
|
"distribution": "internal"
|
|
},
|
|
"preview": {
|
|
"distribution": "internal",
|
|
"env": {
|
|
"EXPO_PUBLIC_API_URL": "https://pawfeed.org",
|
|
"EXPO_PUBLIC_CLERK_PUBLISHABLE_KEY": "pk_live_Y2xlcmsucGF3ZmVlZC5vcmck",
|
|
"EXPO_PUBLIC_SUPABASE_URL": "https://gqhsovpcfgffdtjxumyy.supabase.co"
|
|
}
|
|
},
|
|
"production": {
|
|
"env": {
|
|
"EXPO_PUBLIC_API_URL": "https://pawfeed.org",
|
|
"EXPO_PUBLIC_CLERK_PUBLISHABLE_KEY": "pk_live_Y2xlcmsucGF3ZmVlZC5vcmck",
|
|
"EXPO_PUBLIC_SUPABASE_URL": "https://gqhsovpcfgffdtjxumyy.supabase.co"
|
|
}
|
|
}
|
|
},
|
|
"submit": {
|
|
"production": {}
|
|
}
|
|
}
|