fix: [SDK-4513] re-display queued in-app messages on unpause

[claude]

Requested by Fadi George · Slack thread

Before / After

• Before: Turning off pause (InAppMessages.Paused = false) left in-app messages that had been queued while paused stuck in the display queue. They would not show until the next session boundary (app backgrounded 30+ seconds, then foregrounded).
• After: Those already-queued messages display immediately on unpause, as the documentation implies ("Changing the value to false resumes normal message delivery for users who qualify based on their triggers").

How

While paused, attemptToShowInAppMessage() early-returns, so messages stay parked in messageDisplayQueue. On unpause the paused setter previously called only evaluateInAppMessages() — which re-evaluates triggers but only drains the queue for messages that newly qualify (via queueMessageForDisplay()). Messages already sitting in the queue were never re-attempted.

The fix adds an attemptToShowInAppMessage() call to the if (!value) unpause branch of the setter, ahead of the existing evaluateInAppMessages() call, so the existing queue is drained first and then triggers are re-evaluated. Both calls run inside the existing suspendifyOnDefault { } block.

File: OneSignalSDK/onesignal/in-app-messages/src/main/java/com/onesignal/inAppMessages/internal/InAppMessagesManager.kt

Linked issues

• Linear: https://linear.app/onesignal/issue/SDK-4513
• Fixes [Bug]: InAppMessages.Paused = false does not re-attempt display of queued IAMs mid-session #2647

---

Generated by Claude Code

[github-actions]

📊 Diff Coverage Report

Diff Coverage Report (Changed Lines Only)

Gate: aggregate coverage on changed executable lines must be ≥ 80% (JaCoCo line data for lines touched in the diff).

Changed Files Coverage

• InAppMessagesManager.kt: 1/1 touched executable lines (100.0%) (3 touched lines in diff)

Overall (aggregate gate)

1/1 touched executable lines covered (100.0% — requires ≥ 80%)

📥 View workflow run