I need to elicit the location of the user in the Siri intents and so I call: override init(){ super.init() self.locationManager=CLLocationManager() self.locationManager.delegate = self; self.locationManager.startUpdatingLocation() self.locationManager.requestWhenInUseAuthorization() } Still neither public func locationManagerDidChangeAuthorization(_ manager: CLLocationManager) nor public func locationManager(_ manager: CLLocationManager, didUpdateLocations locations: [CLLocation]) are ever called, notwithstanding the presence of the correct entry in the info.plist, the inclusion of the library and the indication of the delegation with: class IntentHandler: INExtension, INSendMessageIntentHandling, CLLocationManagerDelegate, UISceneDelegate are ever called. Is there any problem with CLLocation manager on intents? What would be a big problem as there is no way to share information with the main app!

Hello, I’m developing an iOS app focused on B2B scenarios, specifically for certain companies to track their employees’ real-time (live update) locations. Because the app continuously updates location data in the background (and can re-enable tracking after a force quit), battery usage can sometimes be relatively high. The app is not intended for the general public and is only meant for these specific companies and their employees. Therefore, I’m not considering a fully public App Store release. With that in mind, I’d appreciate some advice on: The most suitable distribution method for an app intended for multiple organizations but restricted to a closed group (e.g., Apple Business Manager - Custom Apps?). Any particular guidelines or best practices regarding continuous background location tracking, especially in terms of battery impact. Additional permissions or disclaimers Apple may require for re-enabling location tracking after a force quit. Thank you in advance!