My main issue is what code is actually using the apis that Apple is complaining about. Eg, these are the ones in the email I received:
NSPrivacyAccessedAPICategoryDiskSpace
NSPrivacyAccessedAPICategoryFileTimestamp
NSPrivacyAccessedAPICategoryUserDefaults
Ok, the last one I understand. I am using UserDefaults. But I don't know who's using the first 2, although I might guess that it's also UserDefaults under the hood?
jacko3232
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Post
Replies
Boosts
Views
Activity
Having the same issue with an app that was working fine a few months ago, it went dormant, and now trying to do some more work on it. The app will do all sorts of async things, but I'm getting this right on the main thread as shown by the image below. The code the warning shows up on is below. It points to the line with "@main". And the stack trace is also just there (shows boilerplate code).
@main
struct MyApp: App {
var body: some Scene {
WindowGroup {
ContentView()
}
}
}
Now, because a previous poster mentioned AdMob, I commented that out and the warning went away. I fixed it by just moving the AdMob init code into an async function, and that took care of the warning.
BUT JESUS! How about generating a warning that makes sense? Point to the line with the admob code!
OMG, this is so awful. I was able to plug in my iPhone directly into my laptop running Xcode and was able to run an app i'm building from Xcode no problem. I then tried my wife's iPhone, nothing. I mean....nothing. Both phones have the exact same version of iOS installed.
Rebooting the laptop, rebooting the phone, restarting everything, and still nothing. I keep getting the "Failed to prepare device for development, please unlock and reconnect your device", which I've tried countless times to no avail.
How can things be broken so bad?
This had to do with not having a developer account. The instructions do say you need one, which i missed.
Running into this with xcode 13 on Monterrey. Shut down Xcode, and the cpu was still being consumed to the point that you could hear the machine. Using top found that a process called "swift-frontend" was the culprit. Did a "kill " and that took care of that.