AdminConsole
← All SDKs and distributions
iOS · Binary distribution

[MapplsAPICore]()

Mappls API Core Native for iOS distributed via the SPM (Swift Package Manager).

distributionEntitlement And Compatibility Reviewstateless
Entitlement And Compatibility Review

Compatibility decision

Use for artifact discovery only. Confirm entitlement and the exact SDK, native artifact, toolchain, architecture, and host-application version pairing.

Repository content, activity, code fragments, and local correspondence are discovery evidence only. They do not establish a supported package coordinate, binary identity, current version, account entitlement, runtime pairing, production compatibility, or approval.
PlatformiOSNo implementation language identified in the source snapshot
Source activityActiveLast repository push 2026-06-30
CorrespondenceUnmatched0 minimized local candidates; candidates are not compatibility proof
Captured documentation8 sections0 source samples · 18 endpoint signals
Scope

Products and prerequisites

Routes & NavigationCapture & Feedback
  • An iOS project with Xcode and the package manager required by the source release
  • The corresponding product entitlement enabled for the developer application
Captured source evidence

Install and configuration guidance

These statements are reproduced as normalized repository evidence. Validate coordinates and versions before copying them into a project.

1 matching sections

Installation

To add a package dependency to your Xcode project, select File > Swift Packages > Add Package Dependency and enter its repository URL. See Adding Package Dependencies to Your App.

From discovery to release

Connected implementation paths

Exact source paths

No quickstart or starter explicitly names this source. Continue through the platform path without claiming direct lineage.

Migration evidence

No published migration track names this source. Lifecycle and compatibility review still apply.

Release gate

Production compatibility checklist

A clean demo is the beginning of the decision, not its conclusion.

  1. 01

    Confirm the exact package or artifact identifier and version with the owning Mappls product team; a repository name is not a package contract.

  2. 02

    Verify platform toolchain, operating-system, architecture, host-application, and transitive-dependency compatibility from a clean build.

  3. 03

    Bind only the documented credential class and restriction to its intended client or trusted-server runtime; never commit or log a secret.

  4. 04

    Verify account entitlement, region, quota, endpoint generation, data rights, and applicable commercial terms independently.

  5. 05

    Exercise initialization, ready, denied, empty, offline, timeout, cancellation, background/resume, and teardown paths.

  6. 06

    Pin dependency and native artifact integrity evidence; retain source fingerprint, selected version, lockfile, build provenance, and approving owner.

  7. 07

    For stateful or hybrid behavior, persist application state outside the SDK and prove idempotency, reconciliation, audit, privacy, and recovery.

  8. 08

    Release by a bounded cohort with observable rollback; repository activity or a successful fixture is never production compatibility evidence.

Private correspondence

Local repository candidates

Only minimized identity evidence is exposed. Review candidates side by side; do not assume they are the same release line.

No deterministic local candidate was found for this public source.