Not a very comforting message. When shall you port Api functions to Swift not to have to make those strange concoctions, just to have it compiling?

Still it seems Apple is progressively checking all those annotations as errors. I hope, though, before that happens, all affected code shall be ported to swift, instead go bringing along Objective-C code.

Still now it gives no error, and that is quite good for me, having bounced my head against a wall for a month trying to port my app to Swift 6...

Non-'@objc' method 'locationManager(:didFailWithError:)' does not satisfy optional requirement of '@objc' protocol 'CLLocationManagerDelegate' ) Requirement 'locationManager(:didFailWithError:)' declared here (CoreLocation.CLLocationManagerDelegate.locationManager) and many more of the same kind I have no space to insert in this comment.

func application( _ application: UIApplication, handleEventsForBackgroundURLSession identifier: String, completionHandler: @escaping () -> Void) has no async version, differently of many other functions. So I need to store that completion handler somewhere in order to use it, but it is not clear where without producing errors.

Of course I also sue Swift 6. The app delegate function just has the completion handler and no version with async and throws. And I need to store it in an actor to check that is not used by different threads contemporarily. So I do not understand why your version produces no error and mine does.

As a matter of fact I moved everything in the actor and the error went away.

Of course the main app has the privacy string in info.plist, as well as the test app, otherwise no message would be delivered. I have no other device where to install the app, but I'm afraid some of my users might have the same problem. How do I revoke the permission, should I switch off the Library and Apple Music switch?

Crashing on the device. It is very hard and demanding to create a new project just for that. But of course if you cannot understand what is the issue with this problem by the crash log, I'l take my time to create a new project extracting this feature.

At any rate I also set a requestAuthorization function that results in authorized, notwithstanding the app still crashes in the same way.

I wish I could; still the error surfaces while the internal apple libraries are executed, as you may see in the published logs that do not even mention files in my own project, but rather an exotic FigCaptureSourceRemote.m file, when my code is just Swift!

I keep updating my feedback assistant thread with no responses by Apple either there or here, and that is quite strange.

I'm using Xcode Version 15.2 (15C500b), because my Mac does not support newer versions.