Troubleshooting In-App

 

In this article, we will look at some of the most frequent problems encountered while using In-Apps and how to solve them.

In-Apps aren't rendering as expected

MoEngage SDK doesn't show the In-App by default like how push notifications work. You are expected to call the following line of code in the screens or for events when you want to show the In-App.

MoEInAppHelper.getInstance().showInApp(context)

 

In-Apps aren't rendering as expected on app open

When you create an In-app campaign with trigger criteria as on App open, you also need to ensure that the following code is called on the app's first screen open. You need to call this code in onResume() of the fragment or onStart() of the Activity.

MoEInAppHelper.getInstance().showInApp(context)

 

In-Apps aren't rendering on the screen name selected

When you create an In-app campaign with trigger criteria as on specific screen, you also need to ensure that the following code is called on the screen name you selected. You need to call this code in onStart() of the Activity or onResume() of the fragment.

MoEInAppHelper.getInstance().showInApp(context)

 

Test In-Apps showing "Something went wrong" error

There could be multiple reasons for this error.

  • Glide dependency missing

Requirements for displaying images and GIFs in InApp

Starting InApp version 7.0.0, SDK requires Glide to show images and GIFs in the in-apps. You need to add the below dependency in your build.gradle file.

Groovy

dependencies {
 ...
 implementation("com.github.bumptech.glide:glide:4.9.0")
 annotationProcessor("com.github.bumptech.glide:compiler:4.9.0")
}

In case you are using kapt in your project replace annotationProcessor with kapt

Previous

Next

Was this article helpful?
0 out of 0 found this helpful

How can we improve this article?