EKAuthorizationStatusAuthorized is declared as an alias of fullAccess and
kCLAuthorizationStatusAuthorized as an alias of authorizedAlways, so in
Calendar, Reminders and Location the branch listed first swallowed the one
below it. Location now says plainly what it always did: always covers either
access level, when-in-use covers only its own.
Calendar and Location kept a Permission.Kind and unpacked it with switches
ending in fatalError, although each type only ever holds its own kind. They
store the access level instead and build the kind from it, which also lets
Calendar request the level directly rather than through two intermediate
closures.
The location handlers no longer implement locationManager(_:didChangeAuthorization:),
deprecated since iOS 14 and never called at the current deployment target.
Location imported EventKit instead of CoreLocation and Bluetooth imported
CloudKit without using it. The German strings file still carried nine keys
from an interface the package no longer ships.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
AVAudioSession.recordPermission and requestRecordPermission are deprecated
since iOS 17 in favour of AVAudioApplication, with the old path kept for
iOS 15 and 16.
PHPhotoLibrary.authorizationStatus() and requestAuthorization(_:) carry
API_DEPRECATED_WITH_REPLACEMENT and, by Apple's own note, report plain
authorized even under limited access; both now go through the access level
variants, available since iOS 14.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
NSHealthShareUsageDescription describes reading samples and
NSHealthUpdateUsageDescription describes writing them, so the two keys were
returned by the wrong properties — apps copying them into Info.plist ended up
with swapped descriptions.
Simplified Chinese lived in zh_Hans.lproj with an underscore, which no bundle
ever matches; the folder is now zh-Hans.lproj like its Traditional sibling.
Motion called stopActivityUpdates() after a query, though that method pairs
with startActivityUpdates and did nothing here. The remaining trick — asking
for an empty date range purely to raise the dialog — is now explained.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The manifest moves to swift-tools-version 6.3 with swiftLanguageModes
[.v6], and the per-product PERMISSIONSKIT_* defines are gone — they only
existed to carve the sources into podspec subspecs, while SPM already
compiles every permission as its own target. Products and targets are now
derived from one list of permission names instead of sixteen identical
blocks.
In the sources that means the conditional import of the core module and
the gates that tested nothing but a define both collapse, Text.bundle
always resolves to .module, and the MIT header leaves all 23 files, as in
the other packages.
For strict concurrency the completion closures become @MainActor rather
than @Sendable: a permission dialog is UI work, and @Sendable would reject
the usual `request { [weak self] in ... }` from a view controller. They are
now called through Task { @MainActor in ... }, copied into a local first
where a delegate would otherwise send a non-Sendable handler; openSettingPage
is main actor isolated and drops its queue hop; the handler singletons are
marked nonisolated(unsafe), and the notification settings lookup keeps only
the Sendable authorization status behind its semaphore.
Also fixes the reqeustUpdate and Ovveride typos and renames the notification
options file that carried "userNotifcation" in its name.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The raised deployment targets make every availability check below iOS 15,
tvOS 15 and watchOS 9 always true, so the legacy branches were dead code:
- BluetoothPermission: collapse the 13.1 / 13.0 / CBPeripheralManager
cascade into CBCentralManager.authorization
- BluetoothHandler: same collapse, and read the authorization from the
class property instead of the instance one deprecated in iOS 13.1,
which also removes the separate visionOS branch
- LocationPermission, LocationAccuracy: drop the iOS 14 fallbacks and a
nested os(iOS) check inside a file already gated on it
- Location handlers: unmark locationManagerDidChangeAuthorization and
read authorizationStatus off the manager instead of the deprecated
class method, collapsing the per-platform ifdefs
- NotificationAccess: announcement and timeSensitive no longer fall back
to alert
- CameraPermission, TrackingPermission: drop the @available on the types
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
After iOS 18, a new status limited was added to CNAuthorizationStatus - ‘This application is authorized to access some contact data.’ In the limited status, I tried using CNContactStore to fetch contact data, and it successfully retrieved the corresponding data selected by the user. Therefore, I believe this status should be treated as authorized.