[Fix] Don't evaluate in app messages when paused

[nan-li]

Description

One Line Summary

Don't evaluate in app messages when paused to improve accuracy once they are unpaused.

Details

Motivation

A SDK consumer reached out with the following issue:

1. Set up a regular IAM and a duration since last IAM
2. Pause IAMs and open app
3. Now unpause IAMs
4. The first IAM will show, then the duration IAM will show immediately after, ignoring the duration

• This is caused by message evaluation after fetching.
• Since no IAM has shown yet in the paused state, the duration IAM passes the duration check and is queued for display
• Thus, evaluating IAMs while paused will lead to inaccuracies once IAMs are unpaused.
• In this case, duration-since-last IAMs will be evaluated incorrectly and then queue for display once unpaused.
• When IAMs are unpaused, IAM evaluation is re-triggered anyway and will queue the messages for display at that time. There is no need to evaluate while paused.

Scope

More accurate In App Message evaluation

Testing

Unit testing

Will be part of a subsequent task to build IAM tests.

Manual testing

iPhone simulator 18.1

• Reproduced issue with 2 IAMs (a display on app open, and a 30 second duration since last)
• In app messaging starts out paused
• Then unpause
• First IAM should display then 30 seconds later the next one should display

Affected code checklist

• Notifications
  • Display
  • Open
  • Push Processing
  • Confirm Deliveries
• Outcomes
• Sessions
• In-App Messaging
• REST API requests
• Public API changes

Checklist

Overview

• I have filled out all REQUIRED sections above
• PR does one thing
• Any Public API changes are explained in the PR details and conform to existing APIs

Testing

• I have included test coverage for these changes, or explained why they are not needed
• All automated tests pass, or I explained why that is not possible
• I have personally tested this on my device, or explained why that is not possible

Final pass

• Code is as readable as possible.
• I have reviewed this PR myself, ensuring it meets each checklist item

---

This change is 

[nan-li]

Here is where evaluateMessages is called when IAMs are unpaused.

[jinliu9508]

Logic looks good to fix this issue. Just curious about a scenario when there is a condition to show IAM when either a trigger is satisfied OR duration > 30 seconds. It looks like the trigger won't work when IAM is paused. Is this what we expect?

[nan-li]

Logic looks good to fix this issue. Just curious about a scenario when there is a condition to show IAM when either a trigger is satisfied OR duration > 30 seconds. It looks like the trigger won't work when IAM is paused. Is this what we expect?

I think this is the expected behavior, since we don't show any IAMs while in the paused state. Are you saying maybe it won't work if IAMs are then unpaused?