Move the explicitly deprecated MapmyIndia iOS tracking line to a release-qualified Mappls SDK while preserving durable session identity, consent, background execution, event order, and unknown-outcome recovery.
Repository lineage identifies a Mappls iOS candidate, but the exact package, Swift/Xcode/deployment matrix, background modes, privacy manifest, credential class, entitlement, and migration behavior require product-owner confirmation.
Legacy sources are fully covered. Candidate links expose the closest public evidence and its maturity; they do not silently upgrade it to an entitlement or support declaration.
mapmyindia-intouch-ios-sdkmappls-intouch-ios-sdkResolve each dimension explicitly. “It compiled” does not prove identity, lifecycle, failure, privacy, or operational compatibility.
SDK initialization and tracking state can hide durable device, user, asset, and session identities.
Persist each identity, expected version, consent revision, and command idempotency key above the SDK.
Start, duplicate start, restart, logout, reinstall, device transfer, and retirement journeys reconcile to one authoritative session.
Historical iOS background, permission, and application-delegate assumptions may no longer hold.
Qualify current authorization, accuracy, background mode, scene, suspension, termination, and relaunch behavior.
Physical-device tests cover denial, reduced accuracy, background, force quit, reboot, low power, offline, and upgrade.
Callbacks or local queues may not expose authoritative ordering or acknowledgement.
Normalize event identity, observed time, sequence, acknowledgement, and reconciliation state outside the SDK.
Duplicate, gap, late, out-of-order, timeout-after-commit, and revoked-entitlement injection produces bounded recovery.
Do not advance on calendar alone. Each stage creates evidence that makes the next one safe and reversible.
Inventory every iOS tracking integration, package, host, credential class, callback, and owner before changing production.
Resolve the exact entitled package or endpoint with Mappls and verify its supported toolchain, region, quotas, authentication, and lifecycle.
Move iOS tracking integration calls behind a narrow application-owned interface without changing product behavior.
Replay approved fixtures and shadow eligible reads while preventing duplicate writes or user-visible duplicate sessions, fixes, or events.
Release to internal users and bounded cohorts with health gates, ownership, automatic stop conditions, and immutable version evidence.
Remove legacy credentials and dependencies only after rollback and audit retention obligations expire.
These examples deliberately model the seam and verification pattern—not unconfirmed package symbols. Implement the adapters only after the exact target contract is issued.
struct TrackingSession: Sendable { let id: String; let expectedVersion: Int }
struct TrackingReceipt: Sendable { let providerId: String; let version: Int; let state: String }
protocol TrackingProviding: Sendable {
func start(_ session: TrackingSession, idempotencyKey: String) async throws -> TrackingReceipt
func reconcile(sessionId: String) async throws -> TrackingReceipt?
func stop(_ session: TrackingSession, idempotencyKey: String) async throws -> TrackingReceipt
}
// Persist session and command identities before invoking the selected SDK.
// On timeout, reconcile the same identity before issuing another command.The candidate and exact package/endpoint versions are approved by the owning Mappls product team for the target account and region.
Journey-level contract tests pass on every supported device, browser, architecture, and release build—not only a debug simulator.
Security, privacy, accessibility, performance, quota, observability, and support owners accept measured differences.
A bounded cohort completes the agreed observation window without an unresolved severity-one or severity-two regression.
Stopping traffic is not enough. Recover durable resources, sessions, events, and in-flight commands without duplicates or hidden divergence.
Prepare support packetKeep the previous signed artifact, dependency lock, configuration, and credential valid until the observation window closes.
Make the provider selection server- or release-controlled; define automatic stop signals and one accountable rollback owner.
For durable state, prove backward-readable records or a reversible data migration before allowing candidate writes.
After rollback, reconcile in-flight requests and resources by stable identifiers instead of replaying commands blindly.