[abdulraqeeb33]

Stack (base feat/never-crash, merged to main as one unit; split out of #2793):

1. refactor: [SDK-5538] add SdkOperation names for init-gated entry points #2800 SdkOperation names
2. feat: [SDK-5538] remote kill switch with a placeholder OneSignalImpV2 #2801 Kill switch with a placeholder OneSignalImpV2
3. feat: [SDK-5538] deferred managers that stand in before init #2802 Deferred managers (this PR)
4. fix: [SDK-5538] never crash on invalid init or calls before init #2803 Never-crash init

Description

One Line Summary

Deferred managers that stand in for User, Notifications, InAppMessages, Session, Location and the JWT listeners before init succeeds.

Details

Motivation

Part of SDK-5538. Today every accessor throws before init. PR 4 hands these out instead, so calls before init log rather than crash.

Scope

• Every call re-resolves the real manager through a ManagerSource, so a reference captured before init (for example through dependency injection) works after init or after a retry.
• Before init, registrations are queued and replayed in order, once: user and push subscription observers, permission observers, notification lifecycle and click listeners, IAM lifecycle and click listeners, JWT invalidated listeners, InAppMessages.paused and Location.isShared.
• The queue does not grow on add and remove pairs: a removal cancels its queued add, and a setting keeps only its latest value. The paused and isShared getters return the queued value.
• Other calls are logged by name and return a default. Suspend members (for example requestPermission) suspend on init instead of blocking.
• A replayed call that throws is logged and the rest still replay.
• Not wired in yet; PR 4 does that. No behavior change.

Testing

Unit testing

DeferredManagersTests: for every manager, non-registration calls are ignored before ready and forward after; registrations queue and replay in order, once; a removal cancels its queued add; a setting keeps its latest value and reads back; suspend members await; a failing replayed call does not stop the rest. All suites, spotless, detekt and apiCheck pass.

Manual testing

Not needed, not wired in.

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