I have the same warning over and over again, this is the most annoying warning Xcode ever spit out. Makes debugging impossible, I am so sick of this!

I don't know if this wasn't the case back than or the review progress is even more flawed than I thought, but I got through with my Screenshots with this answer to their message: "In the App Store Review Guidelines 4.5.2 (ii) Apple Sites and Services (https://developer.apple.com/app-store/review/guidelines/#apple-sites-and-services) the guideline says: "Cover art and other metadata may only be used in connection with music playback or playlists (including App Store screenshots displaying your app’s functionality)" Several of my screenshots show playlist covers (not album covers) created, owned and provided by Apple Music not by the artist who is on the image. The playlist covers are provided by Apple Music via their free AppleMusic API and the framework MusicKit. As you can see under the section 7 "Apple Approval" in the Apple Music Identity Guide (https://www.apple.com/itunes/marketing-on-music/identity-guidelines.html#apple-approval) "Most marketing materials don’t require approval by Apple." " Maybe it helps for the future people who search for this :)

I was skeptical and dismissed this thread which was a mistake. This is not a bug, the vision framework needs a background to detect something. In my case I wanted to check drawn data from PencilKit to be analyzed with Vision. I was able to get really good results with this small workaround to add a background to the drawn content: private func getImage() -> UIImage { let image = canvas.drawing.image(from: canvas.bounds, scale: 1) // use your image here if let data = image.jpegData(compressionQuality: 1), let imageWithBackground = UIImage(data: data) { return imageWithBackground } return image } Its not necessary to save it to files for this. The recognition works without a problem on iOS 16 in my case.

Thank you Ziqiao for your answer! You are right it works with 18.2.1, I didn't bother to check because the issue was active for some iOS releases now. But that leads me to two follow up questions: The issue is only fixed if I set my minimum target to 18.2 and that is quite a bad user experience. So there is no logic for me to fix and I have to accept that this is a bug? Was the issue or the change of some important CoreData logic changes from iOS 17 to iOS 18 somehow communicated or acknowledged somewhere? Because it seems even though in my case it wasn't enough, the linked forum post had multiple users with a similar problem, which some of them fixed with the help of this thread. But other than those 2 threads I couldn't find any information on this. I ask because if changes like these come up in the future I would like to know how to handle these. Thanks for your help! :)