You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been getting this error from our users through our Firebase Crashlytics.
Fatal Exception: java.lang.RuntimeException
Unable to start activity ComponentInfo{com.getcleva.cleva_mobile_app/io.intercom.android.sdk.m5.IntercomRootActivity}: io.intercom.android.sdk.exceptions.IntercomIntegrationException: Intercom was not initialized correctly, Intercom.initialize() needs to be called in onCreate() in your Application class.
I followed the documentation to properly setup for Android.
I created an MyApp.kt file and created a custom android.app.Application class named MyApp with an onCreate() override to initialize Intercom Sdk.
Finally, in my AndroidManifest.xml on the application tag I added an android:name attribute, and set the value to the class' name, prefixed by a dot (.). android:name=".MyApp"
Before shipping to production, it was confirmed and worked properly as expected.
From my investigation, this issue doesn't happen to all my android user, but has affected about 22 users.
The text was updated successfully, but these errors were encountered:
@JustineUgo Can you please confirm if the issue is from your updated app version or older app version? It maybe possible that your users are still having the old app version.
I have been getting this error from our users through our Firebase Crashlytics.
I followed the documentation to properly setup for Android.
I created an MyApp.kt file and created a custom android.app.Application class named MyApp with an onCreate() override to initialize Intercom Sdk.
Finally, in my AndroidManifest.xml on the application tag I added an android:name attribute, and set the value to the class' name, prefixed by a dot (.).
android:name=".MyApp"
Before shipping to production, it was confirmed and worked properly as expected.
From my investigation, this issue doesn't happen to all my android user, but has affected about 22 users.
The text was updated successfully, but these errors were encountered: