Closed Arhane closed 1 year ago
TL;DR The problem was eas
and environment variables
The problem was with the environment variables. I loaded them with dotenv
and used them like process.env.INTERCOM_IOS_AUTH_TOKEN
in app.config.js
. But when I ran the build locally, the build was happening in another folder and didn't have access to environment variables
TL;DR The problem was
eas
and environment variablesThe problem was with the environment variables. I loaded them with
dotenv
and used them likeprocess.env.INTERCOM_IOS_AUTH_TOKEN
inapp.config.js
. But when I ran the build locally, the build was happening in another folder and didn't have access to environment variables
Interesting, I might be having the same issue, when you say it is running in a different folder how did you solve it?
We had the same issue previously (around October 2022). process.env.INTERCOM_ANDROID_TOKEN
in app.config.js
, but no secrets configured at expo.dev, so when it built at Expo's servers it didn't have access to the correct variables, and intercom couldn't be initialized.
Problem:
Using Intercom on android I get the error message
Details
Everything seems fine with internals of the android part of app I build the android folder with
expo prebuild -p android
and checked the contents of theMainApplication.java
At the file startand
onCreate
methodI run my application with
eas build --platform android
and create an expo server withexpo start --dev-client