requestPermission

Backwards-compat API: request and ignore status (logs it)

Requests the specified permission.

This function will suspend until the user grants or denies the permission. If the permission is already granted, this function will return immediately.

Platform behavior

• iOS: Throws IllegalStateException when the consumer app's Info.plist is missing the required usage description key for the requested permission (e.g. NSLocationWhenInUseUsageDescription for FINE_LOCATION, plus NSLocationAlwaysAndWhenInUseUsageDescription for BACKGROUND_LOCATION). iOS silently ignores requests with missing keys, so the SDK surfaces the misconfiguration immediately rather than as a phantom "denied" status with no system prompt.

• iOS — "Allow Once" (iOS 14+): when the user picks "Allow Once" on the location prompt, the granted state lasts only for the current app session. iOS reverts the status to NOT_DETERMINED on the next launch with no callback or notification. Re-check permission status on every launch and viewWillAppear rather than caching across sessions; calling requestPermission again will re-prompt as expected.

• iOS — Reduced Accuracy (iOS 14+): when the user grants location with "Precise Location" off, iOS fuzzes the device location to ~1–5 km. For a FINE_LOCATION request this is reported as PermissionStatus.REDUCED_ACCURACY (not GRANTED) so consumers can prompt the user to enable Precise Location in Settings. Geofencing with small radii is unreliable in this state; isLocationAccuracyReduced() reports the same condition as a boolean.

• Android — Approximate location (Android 12+): when the user downgrades a FINE_LOCATION request to "Approximate", the OS grants ACCESS_COARSE_LOCATION but not ACCESS_FINE_LOCATION; this is reported as PermissionStatus.REDUCED_ACCURACY (not DENIED) — the Android counterpart to iOS reduced accuracy.

• Android: Does not throw on missing <uses-permission> declarations in AndroidManifest.xml — the underlying request is simply rejected by the OS, and the result returns as DENIED (or stays NOT_DETERMINED). Verify your manifest contains the required permissions before calling this method.

Parameters

Throws

Requests the specified permission.

This function will suspend until the user grants or denies the permission. If the permission is already granted, this function will return immediately.

Platform behavior

• iOS: Throws IllegalStateException when the consumer app's Info.plist is missing the required usage description key for the requested permission (e.g. NSLocationWhenInUseUsageDescription for FINE_LOCATION, plus NSLocationAlwaysAndWhenInUseUsageDescription for BACKGROUND_LOCATION). iOS silently ignores requests with missing keys, so the SDK surfaces the misconfiguration immediately rather than as a phantom "denied" status with no system prompt.

• iOS — "Allow Once" (iOS 14+): when the user picks "Allow Once" on the location prompt, the granted state lasts only for the current app session. iOS reverts the status to NOT_DETERMINED on the next launch with no callback or notification. Re-check permission status on every launch and viewWillAppear rather than caching across sessions; calling requestPermission again will re-prompt as expected.

• iOS — Reduced Accuracy (iOS 14+): when the user grants location with "Precise Location" off, iOS fuzzes the device location to ~1–5 km. For a FINE_LOCATION request this is reported as PermissionStatus.REDUCED_ACCURACY (not GRANTED) so consumers can prompt the user to enable Precise Location in Settings. Geofencing with small radii is unreliable in this state; isLocationAccuracyReduced() reports the same condition as a boolean.

• Android — Approximate location (Android 12+): when the user downgrades a FINE_LOCATION request to "Approximate", the OS grants ACCESS_COARSE_LOCATION but not ACCESS_FINE_LOCATION; this is reported as PermissionStatus.REDUCED_ACCURACY (not DENIED) — the Android counterpart to iOS reduced accuracy.

• Android: Does not throw on missing <uses-permission> declarations in AndroidManifest.xml — the underlying request is simply rejected by the OS, and the result returns as DENIED (or stays NOT_DETERMINED). Verify your manifest contains the required permissions before calling this method.

Parameters

Throws