> ## Documentation Index
> Fetch the complete documentation index at: https://moengage-sdk-docs.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting In-App

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

<iframe src="https://www.youtube.com/embed/b9SPaPWzW-c" title="YouTube video player" frameborder="0" className="w-full aspect-video rounded-xl" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen />

## In-Apps aren't rendering as expected.

There are could be multiple reasons for InApps not rendering. 

1. MoEngage SDK doesn't show the In-App by default, like push notifications. When you want to show the in-app, you must call the following line of code to show inapp for app open and screen based inapps. The only exception is custom event in-Apps; you need not call the following method for custom event in-Apps.\
   [*MoEInAppHelper.getInstance().showInApp(context)*](https://moengage.github.io/android-api-reference/inapp/com.moengage.inapp/-mo-e-in-app-helper/show-in-app.html)
2. InApps are not shown when delivery controls aren't met or when some activities are opted out of the in-app optout config while initialising MoEngage SDK. If you have SDK logs enabled, you can see the reason in them.
3. Inapps are synced to the device because of life cycle library integration problems. Use the steps given [here](/developer-guide/android-sdk/troubleshooting-and-faqs/troubleshooting-and-faqs) to troubleshoot them.
4. Inapps couldn't be synced to the device because of the exception in some other library functionality of MoEngage, please check the error logs if you find anything here.

## 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)*](https://moengage.github.io/android-api-reference/inapp/com.moengage.inapp/-mo-e-in-app-helper/show-in-app.html)

## 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)*](https://moengage.github.io/android-api-reference/inapp/com.moengage.inapp/-mo-e-in-app-helper/show-in-app.html)

## Test In-Apps showing "Something went wrong" error

There could be multiple reasons for this error.

* Glide dependency missing

To fix this error please ensure you are adding the glide libraries and also use MoEngage inapp version >= 7.1.4

### **Requirements for displaying images and GIFs in InApp**

Starting InApp version **7.0.0,** SDK requires [Glide](https://bumptech.github.io/glide/) to show images and GIFs in the in-apps. You need to add the below dependency in your **build.gradle** file.

<CodeGroup>
  ```Groovy Groovy theme={"theme":{"light":"github-light","dark":"github-dark"}}
  dependencies {
   ...
   implementation("com.github.bumptech.glide:glide:4.16.0")
  }
  ```
</CodeGroup>