AdminConsole
← All SDKs and distributions
iOS · Binary distribution

MapplsGeofenceUI Plugin for iOS

Mappls Geofence UI Native for iOS distributed via the SPM (Swift Package Manager).

distributionEntitlement And Compatibility Reviewhybrid
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.
PlatformiOSSwift · Text
Source activityAgingLast repository push 2025-06-10
CorrespondenceUnmatched0 minimized local candidates; candidates are not compatibility proof
Captured documentation15 sections14 source samples · 18 endpoint signals
Scope

Products and prerequisites

MapsRoutes & 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.

2 matching sections

Getting Started

Anyone can integrate the Mappls Geofence Plugin by following simple steps.Please note that this Plugin for iOS supports iOS SDK 9.0 and above.

To integrate Geofence SDK, it is important to pass an object of MapplsMapView which is part of Mappls's MapplsMap SDK.

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.

Sanitized repository fragments

Source code evidence

Use these fragments to understand integration shape. They may belong to an older toolchain or authentication generation.

6 shown
Step 3 :- Initialization of GeofenceViewUISwift
import MapplsMap
import MapplsGeofenceUI
var geofenceView: MapplsGeofenceView!
 override func viewDidLoad() {
        super.viewDidLoad()
  // If you're on a background thread and want to execute code on the main thread, you need to call async()
 DispatchQueue.main.async {
let geofenceInstance: MapplsGeofenceView =  {
geofenceView = MapplsGeofenceView.init(geofenceframe: self.view.bounds)
geofenceView?.autoresizingMask = [.flexibleWidth, .flexibleHeight]
 return geofenceView
}()
geofenceInstance.delegate = self
self.view.addSubview(geofenceInstance)
}
}
Step 3 :- Initialization of GeofenceViewUIText
geofenceInstance.delegate = self
Customizing the Geofence using various properties:Swift
geofenceView.setMode(mode: .circle)
Customizing the Geofence using various properties:Swift
geofenceView.isShowDefaultSliderForCircle = false
Customizing the Geofence using various properties:Swift
geofenceView.isShowDefaultModePanel = false
Customizing the Geofence using various properties:Swift
geofenceView.deleteBtnDefaultImage = UIImage(named: "")
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.