All EAS Builds are successful, but after opening the app there is a native crash mentioning that CioSiteId is nil. App.config.js looks like this:
plugins: [
[
"expo-cio",
{
cioSiteId: process.env.CUSTOMERIO_SITE_ID,
cioApiKey: process.env.CUSTOMERIO_API_KEY,
},
],
]
There is an .env file on the project root folder with those values and many others, which are successfully recognized during the build process by EAS (SENTRY_ORG, SENTRY_PROJECT, SENTRY_AUTH_TOKEN, etc). By simply replacing “process.env.CUSTOMERIO_SITE_ID” and “process.env.CUSTOMERIO_API_KEY” for the hard-coded values the crash doesn’t happen anymore.
Remote builds work just fine using Expo Secrets. Is it a bug of eas local builds? I would like to avoid using these hard-coded values on app.config.js and use the local .env file instead.
In your post, please share:
- managed workflow
- eas-cli/0.54.1