AB#277632 - Overlay messaging

[vvoicehovics]

Description of Changes

https://mobius.visualstudio.com/Backstage/_workitems/edit/277632

New Overlay Messaging channel with following API

- OptimoveConfig.Builder........enableOverlayMessaging(sessionLengtHours: = 1h)
- OverlayMessaging.getInstance().resetSession();
- OverlayMessaging.getInstance().setInterceptor(callback)

XRecorder_20260401_03.mp4

Can coexist with in-app

Breaking Changes

• None

Release Checklist

Prepare:

• Detail any breaking changes. Breaking changes require a new major version number, and a migration guide in wiki / README.md

Bump versions in:

• CHANGELOG.md
• gradle.properties
• add links to newly created wiki pages to readme
• Update major version numbers in wiki (basic integration + push guides)

Integration tests

T&T Only

• Init SDK with only optimove credentials
• Associate customer
• Associate email
• Track events

Mobile Only

• Init SDK with all credentials
• Track events
• Associate customer (verify both backends)
• Register for push
• Opt-in for In-App
• Send test push
• Send test In-App
• Receive / trigger deep link handler (In-App/Push)
• Receive / trigger the content extension, render image and action buttons for push
• Verify push opened handler

Deferred Deep Links

• With app installed, trigger deep link handler
• With app uninstalled, follow deep link, install test bundle, verify deep link read from Clipboard, trigger deep link handler

Combined

• Track event for T&T, verify push received
• Trigger scheduled campaign, verify push received
• Trigger scheduled campaign, verify In-App received

Release Procedure

• Squash and merge dev to master
• Delete branch once merged

[wiz-190b289812]

Wiz Scan Summary

Scanner	Findings
Vulnerabilities	-
Sensitive Data	-
Secrets	-
IaC Misconfigurations	-
SAST Findings	7
Software Management Findings	-
Total	7

View scan details in Wiz

To detect these findings earlier in the dev lifecycle, try using Wiz Code VS Code Extension.

[vvoicehovics]

1. views set status bar color to black to prevent random color bar from activity show on top of styled in-app (black kind of fits all if i recall rationale). So, color is set, then unset when view closed.
2. Now as we have overlay + in-app potentially showing simultaneously, their sets-unsets can leave it in incorrect state (e.g. 2nd unset changes it to the 1st set)
3. dialog also does Theme_Translucent_NoTitleBar_Fullscreen, which in theory should prevent any bar showing at all. This is what i observe in test app, this is what AIs conclude, though this is too specific for them not to get creative.
4. i cant categorically confirm setting color is not needed on any devices, the repository which had original rationale doesnt exist anymore.

so, the outcome here is to let in-app do what it was doing and the new channel doesnt touch status color until we have issues. I think this is better vs creating complex implementations for phantom problems we maybe had years ago

@graciecooper or you have idea why it's needed? there is related PR from @k-antipochkin here #63

[graciecooper]

Ya, I’m happy to leave it as-is for now rather than pre-emptively solving a problem that might not actually be a problem

[graciecooper]

sorry i've stolen your version number with a new bugfix ! 😎