Try DSA registration after erasing the browser History/Cash.

I'm using startRelativeAltitudeUpdates with a barometric reference for altitude and subjectively (tested with iOS 17.5 today) the frequency of updates is the same as it used to be in iOS 16 or 15. I wonder if you have location accuracy at max and distance filter at min, as you mention slower updates and location based altitude. What if Apple linked startAbsoluteAltitudeUpdates totally to a location data and you have low frequency filter/accuracy on you CLLocationManager?

Per here: https://developer.apple.com/documentation/corelocation/cllocationupdate/liveconfiguration/automotivenavigation CLLocationUpdate.LiveConfiguration.automotiveNavigation The value that configures positioning for an automobile following a road network. It is about accuracy and distance filter requirements for the location module? Also about "glueing" you to the automotive roads or not. Do you believe this should also discriminate for the .automotive activity only? I watched this WWDC session a long time ago though. From the experience with how the current location/motion works, I'd say my apps would miss a lot of driving distance if they rely on discriminating automotive activity solely by Apple's categorisation.

Same warning happens to me for the app that uses SumUp SDK when using Xcode 16 beta 6. Same static framework shows no warnings in Xcode 15. Created an issue for SumUp on github, but can it be Xcode 16 beta issue? https://github.com/sumup/sumup-ios-sdk/issues/150

UPDATE 1. It started to work as expected after the iPhone restart. UPDATE 2. After changing Siri responses to "Automatic" or "Silent" and then changing back "Prefer Spoken Responses" - Siri never speaks the result's IntentDialog text again, until the iPhone restart. This lady got a character!

UPDATE 3. Siri just does what it wants to do. There is a period it goes by your "Prefer spoken response" and it speaks out your IntentDialog response, then 30 minutes later it only says "That's ok". I guess this is just by "design", it is not meant to be reproducible :):).

Just to clarify "Changing the code to avoid warnings:" - the only warning is exactly to update to: @preconcurrency import WebKit.

Not a direct answer, just sharing my experience: After some Xcode update, I had to replace all @-1 literals with explicit NSNumber initializers like this: ret.availableScales = @[[NSNumber numberWithInt:-1], @0, @1]; For some reason, @-1 wasn’t being evaluated correctly for my code anymore in some places. I contacted Apple about it, but they couldn’t reproduce the issue at the time with simple code. Looks like objective-c literals support is more and more lagging behind. Can you use static/const strings?