Hello all! Apple presented the all-new Core Location Monitor at WWDC 2023. It changes the logic of monitoring for iBeacons with a new approach of adding CLCondition-s for monitoring iBeacon values like UUID, major, and minor. This, I suppose (please do feel free to correct me) is meant to replace current (now deprecated) startMonitoring implementation. Now, we it's a fact that it is impossible to monitor more than 20 regions at once. Question: does the new CLMonitor let us bypass this limit? If not, what's the maximum number of CLConditions we can add to a CLMonitor?

Hello, I have a few questions regarding the new CLMonitor that would be really helpful to hear answers to: How many conditions can the CLMonitor monitor at once? The analogous CLRegions had a limit of 20 in iOS 16. Is there a limit, or a larger limit with CLMonitor? What's the range of radii that CircularGeographicCondition can monitor? With CLRegions, we observed a functional minimum radius of 100m. Finally, the session video notes that CLMonitor events can arrive unpredictably: can any further elaboration be given on these events? When might there be more or less predictability of these events? Thanks! Liam

When running Xcode 15.0 beta, and targeting watchOS 10.0, I'm getting the following error message when I invoke the object. I am using the line import CoreLocation at the top of my ContentView.swift directly below the line import SwiftUI. 'CLMonitor' is unavailable in watchOS