Articles in this section

Testing and Troubleshooting In-App Messages

Fixing the issue

# In this article

# Troubleshooting

By default, when an in-app message is sent, it sits on server queue. It gets pulled by SDK when App is in the foreground. You can see which in-app messages are in the queue by sending a test campaign and then calling GET /api/inApp/getMessages.

The GET request will then return all the messages in the queue and you can determine if you sent the message to the right location.

# iOS in-app message is not shown

Make sure you call IterableAppIntegration from didReceiveRemoteNotification:

// In AppDelegate.swift
func application(_ application: UIApplication, didReceiveRemoteNotification userInfo: [AnyHashable : Any], fetchCompletionHandler completionHandler: @escaping (UIBackgroundFetchResult) -> Void) {
    IterableAppIntegration.application(application, didReceiveRemoteNotification: userInfo, fetchCompletionHandler: completionHandler)
}

# Android in-app message is not shown

If you are implementing your own onMessageReceived() and onNewToken() methods, make sure you forward onMessageReceived() and onNewToken() calls to IterableFirebaseMessagingService.handleMessageReceived and IterableFirebaseMessagingService.handleTokenRefresh respectively.

@Override
public void onMessageReceived(RemoteMessage remoteMessage) {
    IterableFirebaseMessagingService.handleMessageReceived(this, remoteMessage);
}

# No messages received

If you do not see messages received during troubleshooting, verify your notification setup. Iterable uses silent push to alert the app when in-app is available. Follow this guide to see if you have push notifications set up correctly.

In iOS, make sure you have Background Fetch enabled for your app:

Background Modes

# Further reading

User guides:

Developer documentation:

Related articles