Following are debugging instructions in case your In-App Messages are not showing.
Instructions on how to validate and test In-App Messages in the Copilot.cx console can be found in our Knowledgebase.
Debugging the Copilot.cx In-App messaging system
This section is for developers running validation that In-App messages are operational in the app.
You can validate that the Copilot.cx system has downloaded the users In-app messages by looking for the following log entries:
These log entries show the number of In-App Messages waiting to be triggered for this user
[:INFO:]:messagesArrived(messages:):Retrieved in app message list with size 1
[:INFO:]:messagesArrived(messages:):Number of messages after filtering unsupported messages 1
Retrieved in app message list with size = 1, after filtering messages list size is 1
If you do not see these calls in the log, the Copilot.cx session is not active, and the In-App messages have not downloaded.
- Make sure you have correctly added an Event Log Provider from the iOS or Android configuration steps.
- Validate that a session for the correct user is active and you can see the events for this user arriving correctly a the Copilot.cx system(Troubleshooting events).
- On Android, if your app is a single Activity app, at least one event must be called to trigger a "App is Active" triggered message.
Contact your Techincal Onboarding Manager with any questions