Skip to content

Commit

Permalink
missed a nit
Browse files Browse the repository at this point in the history
  • Loading branch information
Bucimis authored and internetisaiah committed Oct 30, 2024
1 parent 76fed09 commit 528bb05
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion _includes/inapp_message_troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ Triggers take time to sync to the device on session start, so there can be a rac

Most in-app message issues can be broken down into two main categories: delivery and display. To troubleshoot why an expected in-app message did not display on your device, confirm that the [in-app message was delivered to the device](#troubleshooting-in-app-message-delivery), then [troubleshoot message display](#troubleshooting-in-app-message-display).

### Troubleshooting In-app message delivery {#troubleshooting-in-app-message-delivery}
### Troubleshooting in-app message delivery {#troubleshooting-in-app-message-delivery}

The SDK requests in-app messages from Braze servers on session start. To check if in-app messages are being delivered to your device, you'll need to make sure that in-app messages are being both requested by the SDK and returned by Braze servers.

Expand Down

0 comments on commit 528bb05

Please sign in to comment.