Gate kit startup on hasConsent

[sorinc03]

Summary

This PR adds a consent gate for integration kit startup.

• Introduces hasConsent on MParticleOptions and MParticle (default: false)
• Prevents kits from initializing/configuring/starting until consent is granted
• Core (non-kit) SDK behavior continues to initialize and operate as normal
• Documents usage in README.md (new Consent section after Kits)

Details

• hasConsent == false:
  • Kit initialization and kit configuration are deferred/cached (no kit start)
• hasConsent transition false -> true:
  • Initializes kits and applies any deferred kit configuration
  • Preserves existing identity-based deferral behavior for configurations that require MPID/consent filtering

API / Usage

• Start kits immediately: set options.hasConsent = true before start(...)
• Defer kits: start with default false, then later set MParticle.sharedInstance().hasConsent = true

(Examples included in README.md.)

Tests

• ✅ xcodebuild test (iOS Simulator) PASSED
  • Executed 821 tests, 0 failures
  • Result bundle: /tmp/mparticle-test-results.xcresult
• Added new coverage: UnitTests/ObjCTests/MPKitConsentGateTests.m

Notes / Compatibility

• Apps that rely on kits starting immediately should explicitly set hasConsent = true at startup to preserve prior behavior.
• Gating is applied at kit init/config/start boundaries; non-kit SDK logic should be unaffected.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c1e2869c0c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Flush cached kits even when consent is not granted

The consent gate returns before the null-config handling, so when configureKits is called with kitConfigurations == nil while hasConsent is NO, we never execute the flushSerializedKits path that previously cleared stale kit state. Because deferredKitConfiguration_PRIVATE is then also nil, a later hasConsent = YES transition falls back to cached kit configs and can start kits that the latest server config intentionally removed.

Useful? React with 👍 / 👎.

[sorinc03]

Can you address the issues and update?

[chatgpt-codex-connector]

Start deferred kits even when launch options are nil

The new delayed-start fallback only runs when launchOptions is non-nil, but normal app launches can legitimately have nil launch options. In consent-gated flows where kits are initialized after UIApplicationDidFinishLaunchingNotification has already fired, this condition prevents start from being called and leaves those kits (notably sideloaded ones initialized via startKitRegister) permanently inactive.

Useful? React with 👍 / 👎.

[sorinc03]

Can you address the issues and update?