Standalone watchOS not displaying location authorisation dialog

Question

DrMickeyLauer OP

Created Oct ’24

Replies 3

Boosts 0

Participants 2

This is a standalone SwiftUI app w/ watchOS 11. To make things simple, I'm using the new concurrent API, like that:

for try await update in CLLocationUpdate.liveUpdates() { … }

watchOS is supposed to show the auth dialog, but it doesn't show up, even though update.authorizationRequestInProgress is true.

What could be the reason?

(Note that I also tried with the procedural old CLLocationManager API, it doesn't work that way as well)

Answered by DrMickeyLauer in 807952022

The answer in this case is plist keys. Here's the deal: While the old location APIs with CLLocationManager had runtime assertions for checking the required NSLocation{xyz}UsageDescription keys – thus crashing, if they were not present – the new APIs just silently ignore missing usage descriptions.

Please consider the case closed – other than considering better diagnostics for this case as a feature request.

Boost

Answer 1

Engineer OP

Apple

Oct ’24

Our engineering teams need to investigate this issue, as this might indicate an issue with watchOS 11.

We'd greatly appreciate it if you could open a bug report, include crash logs and sample code or models that reproduce the issue, and post the FB number here once you do.

We will also need a debug level log. if you could please go to https://developer.apple.com/bug-reporting/profiles-and-logs/ and follow the instructions for Location Services for watchOS to install a logging profile on your device(s). Then reproduce the issue, and follow the instructions at the above link to create a sysdiagnose. And attach that to the Feedback report as well.

Bug Reporting: How and Why? has tips on creating a successful bug report.

Argun Tekant /  DTS Engineer / Core Technologies

0

Answer 2

DrMickeyLauer OP

Oct ’24

FB15415457

0

Answer 3

DrMickeyLauer OP

Oct ’24

Accepted Answer

The answer in this case is plist keys. Here's the deal: While the old location APIs with CLLocationManager had runtime assertions for checking the required NSLocation{xyz}UsageDescription keys – thus crashing, if they were not present – the new APIs just silently ignore missing usage descriptions.

Please consider the case closed – other than considering better diagnostics for this case as a feature request.

0