Native iOS SDK: Access Control, Telemetry and Crash Reporter

Install DevGuardSDK from CocoaPods

Add the published DevGuardSDK pod to your Podfile and pin a version that matches the public documentation. Run pod install in CI so the resolved lockfile stays reproducible across developer machines and release agents.

Create one DevGuard project per iOS bundle identifier. Keep secrets out of the repository and inject them through Xcode configurations or your CI secret store. Agency-managed apps should document who retains project ownership after delivery.

• Confirm the CocoaPods version matches the docs page.
• Commit Podfile.lock for reproducible App Store builds.
• Use separate projects for TestFlight and production when policies differ.
• Document the handover path for client-owned workspaces.

Bootstrap protection before the main UI becomes interactive

Initialize the SDK early in the app lifecycle so remote status can present a warning or lock experience before sensitive screens appear. Model governance as explicit states and keep navigation for product features separate from the control layer.

Respect App Transport and background rules. Heartbeats and refresh schedules should tolerate brief offline periods without creating navigation loops when the app returns to the foreground.

Telemetry, privacy and App Store review readiness

Collect only the device and app signals the dashboard needs. Compact payloads reduce radio time and make periodic check-ins practical on cellular networks. Explain optional advanced telemetry in the host app privacy materials and give project owners clear toggles.

Avoid shipping credentials, session tokens or full user records in telemetry or crash metadata. Review App Privacy answers whenever you enable a new optional metric.

Use the standalone crash reporter correctly

Native iOS keeps DevGuardCrashReporter as a dedicated module alongside the licensing SDK. Capture fatal crashes with build version and platform context, and verify that dSYM uploads cover the architectures you ship.

Trigger a controlled test crash in a staging project before release. Confirm the event appears with a readable stack and is labeled so it cannot be confused with production traffic.

iOS release verification checklist

Test status transitions on a physical iPhone and, when relevant, an iPad. Confirm unlock keys, on-device messaging, offline cache behavior and version reporting after a force-quit. Re-run checks after Xcode, iOS or SDK upgrades.

After launch, watch device check-ins and crash groups, review team permissions and rehearse emergency restore. A remote-control feature is ready only when the team can reverse a change and support the end user promptly.