Skip to content

Restore CLRegion.contains handling for non-circular regions on macOS/watchOS #62

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
SoundBlaster merged 1 commit into from
Nov 15, 2025
Merged

Restore CLRegion.contains handling for non-circular regions on macOS/watchOS #62

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 13 additions & 2 deletions Sources/SpecificationKit/Providers/LocationContextProvider.swift
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -481,9 +481,20 @@
return distance <= circularRegion.radius
}

// CLRegion.contains(_:) is deprecated across Apple platforms, so we only
// evaluate circular regions directly. Non-circular regions fall back to false.
// For non-circular regions (e.g., beacon regions, custom regions),
// use the deprecated CLRegion.contains(_:) on platforms where it's still available
#if os(macOS) || os(watchOS)
// CLRegion.contains(_:) is deprecated but still functional on macOS and watchOS
// Suppress the deprecation warning as we need to support non-circular regions
if #available(macOS 11.0, watchOS 7.0, *) {
return region.contains(currentLocation.coordinate)
}
return false
#else
// On iOS and other platforms where CLRegion.contains(_:) is unavailable,
// non-circular regions cannot be evaluated
return false
#endif
}
}

Expand Down