[Mappls Map SDK]()
Mappls Map Native for iOS distributed via the SPM (Swift Package Manager).
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.Source and identity
- Public source
- Open repository ↗
- Captured document
- Open source documentation ↗
- Default branch
main- Lifecycle risk
- Compatibility Review
- Authentication signals
- oauth2 · api-key
Products and prerequisites
- An iOS project with Xcode and the package manager required by the source release
- OAuth client credentials issued for the intended Mappls project
- A Mappls project key restricted to the intended app, domain, or backend
- The corresponding product entitlement enabled for the developer application
Install and configuration guidance
These statements are reproduced as normalized repository evidence. Validate coordinates and versions before copying them into a project.
Getting Started
Mappls's Map SDK for iOS lets you easily add Mappls Map and web services to your own iOS app. Mappls's Map SDK for iOS supports iOS SDK 9.0 and above and Xcode 10.1 or later. You can have a look at the map and features you will get in your own app by using the Mappls's Maps app for iOS. The SDK handles map tiles download and their display along with a bunch of controls and native gestures.
Dependencies
This library depends upon MapplsAPICore, MapplsAPIKit. All dependent libraries will be automatically.
• For iOS9 or later, make this change to your info.plist (Project target > info.plist > Add row and set keys NSLocationAlwaysAndWhenInUseUsageDescription, NSLocationWhenInUseUsageDescription, NSLocationAlwaysUsageDescription). As follows
Message should be appropriate, according to use of your application.
Source code evidence
Use these fragments to understand integration shape. They may belong to an older toolchain or authentication generation.
<key>NSLocationAlwaysAndWhenInUseUsageDescription</key>
<string>Your location is required</string>
<key>NSLocationAlwaysUsageDescription</key>
<string>Your location is required</string>
<key>NSLocationWhenInUseUsageDescription</key>
<string>Your location is required</string>MapplsMapAuthenticator.sharedManager().initializeSDKSession { isSucess, error in
if let error = error {
// Map cannot be initilize
print("error: \(error.localizedDescription)")
} else {
// Map is authorized sucessfully.
}
}[[MapplsMapAuthenticator sharedManager] initializeSDKSession:^(BOOL isSuccess, NSError * _Nullable error) {
if (isSuccess) {
// Map is authorized sucessfully.
} else {
// Map cannot be initilize
}
}];#import
@interface ViewController () <MapplsMapViewDelegate>
@end
@implementation ViewControllerimport MapplsMap
class ViewController: UIViewController, MapplsMapViewDelegate {
override func viewDidLoad() {
super.viewDidLoad()
let mapView = MapplsMapView(frame: view.bounds)
mapView.autoresizingMask = [.flexibleWidth, .flexibleHeight]
view.addSubview(mapView)
}
});<key>NSAppTransportSecurity</key>
<dict>
<key>NSAllowsArbitraryLoads</key>
<true/>
</dict>Connected implementation paths
Exact source paths
Quickstart · iOSCreate a lifecycle-safe iOS mapDownloadable starter · iOSiOS view-ownership starterAdjacent platform paths
Migration evidence
Direct LineageiOS map and API package lineageProduction compatibility checklist
A clean demo is the beginning of the decision, not its conclusion.
- 01
Confirm the exact package or artifact identifier and version with the owning Mappls product team; a repository name is not a package contract.
- 02
Verify platform toolchain, operating-system, architecture, host-application, and transitive-dependency compatibility from a clean build.
- 03
Bind only the documented credential class and restriction to its intended client or trusted-server runtime; never commit or log a secret.
- 04
Verify account entitlement, region, quota, endpoint generation, data rights, and applicable commercial terms independently.
- 05
Exercise initialization, ready, denied, empty, offline, timeout, cancellation, background/resume, and teardown paths.
- 06
Pin dependency and native artifact integrity evidence; retain source fingerprint, selected version, lockfile, build provenance, and approving owner.
- 07
For stateful or hybrid behavior, persist application state outside the SDK and prove idempotency, reconciliation, audit, privacy, and recovery.
- 08
Release by a bounded cohort with observable rollback; repository activity or a successful fixture is never production compatibility evidence.
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.