I'm having the same issue with the iPhone Duo simulator with the Xcode 27.1 production version. Setting preferredScreenEdgesDeferringSystemGestures to any value doesn't help. As noted it's top 20 or 24px that "eat" the touches in unfolded landscape iPhone Duo simulator orientation.

Worried after seeing this thread I was testing today on iOS 27b8 and beacon enter/exit has not failed me yet. Background/foreground, cold runs - all worked. And on iOS 26.6.1 I didn't notice any issue as well - testing every day.

Same here with the beta version, 3 days, still waiting for review.

My beta version has been waiting for review for 3 days. Looks like general delay/holidays maybe?

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?

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

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 :):).

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!

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

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.

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?

Try DSA registration after erasing the browser History/Cash.

Looks like that for the companies, address and phone will be published. For my company, Apple already shows address, DUNS and phone/email in the Provider section in the AppStore. They called me from the Czech Telecommunication office as told that it is up to a online platform to publish it online or not. I don't know if this will be published for the individual account as well, my individual DSA information is still under review as they required to scan and attach business/court documents. If they publish that in the App Store, you are welcome to visit me!

I'm a small entrepreneur from the Czech Republic and I also don't know if I'm a trader or not. I'm inclined to think that I'm a trader, per definition of DSA, but I'm not sure that my private address should be published in the App Store, available to everyone. We had a story with the digital postal mail boxes here where they started to publish every digital mail box owner address, but they had a privacy related pushback. Now you can select if you want or don't want to have your address published online if you have a digital mail box. I called to our National office of telecommunication that is established as a National Digital Services Act coordinator for Czechia and they promised to be back to me tomorrow with explanations/statement.

Same problem here when seeing crashes from production on iOS 17.0 - 17.1. Added a feedback to Apple as well. I actually went through crash reports and the issue is happening on the current iOS 17.2 beta as well, no fix there.