Is the DNG you are using for the warm-up one that was captured on iPhone? I.e., does it have the same dimensions as the ones captured by the user later?

Did you always process the same image? How is your CIContext set up? Do you maybe have a small sample project we can use to test this? Thanks!

We are suddenly getting the same warning, and we are pretty sure that we (or any library) don't use said API. Are there any other APIs that trigger the warning? Was that list recently extended?

Also filed as FB17081255, including a sample project. Thanks for looking into this!

Did you find the root cause and/or a solution for the problem? I can't reproduce the issue myself, but we have users reporting freezes of our apps that might be related to this issue.

What do you mean by "calling back to the CPU" exactly? The main CPU load of Core Image actually comes from the filter graph optimization CI does before the actual rendering. And unfortunately there is not much you can do to speed this up.

There is a newish API for deferred photo processing, which makes the whole capture process seem much faster. That's probably what the Camera app is doing under the hood. Check out this WWDC session for details.

You can easily test Apple Intelligence features in the EU on an iPad. You just have to set the system and Siri language to English (US) and sign in with a US Apple account under iCloud → Media & Purchases. It even works with sandbox accounts! So if you don’t have a US account, you can easily create a sandbox one in App Store Connect. Also note that Apple Intelligence is available on macOS in Europe without the need for a US Apple account. You just have to set the languages to English.

It turns out this issue is most notable for Mac Catalyst apps that use the Mac Idiom. We built a small package that provides a better alternative to the system default Image Playground: BetterImagePlayground. See screenshots on GitHub for comparison.

More countries will be supported in April. Regardless, Apple Intelligence is only be available on iPhone 15 Pro and newer.

There is also an API that has an optional soureImage instead of the URL: imagePlaygroundSheet(isPresented:concepts:sourceImage:onCompletion:onCancellation:)

Feedback filed: FB16090123

Hi J, Thanks for the response! Yes, Apple Intelligence is enabled on my Mac. When I run the app as "real" Mac Catalyst app, it's actually working. I filed FB16077581 for this, including a very minimal sample project. The following should be enough when added to a new iOS app project: struct ContentView: View { @State var playgroundVisible = false var body: some View { Button(action: { playgroundVisible.toggle() }, label: { Label("Show Image Playground", systemImage: "apple.image.playground") }) .padding() .imagePlaygroundSheet(isPresented: $playgroundVisible) { url in print("Image generated: \(url)") } } }

Have you exported the image from Photos to check with another app if the background is really white? It might be that Photos just visualizes transparency with white.

It could be a problem that you are getting the currentDrawable outside the Operation. If your rendering can't keep up with the draw requests, the operations will pile up while also holding locks on the view's drawable. Instead, you could get the view's drawable inside of the operation and discard the whole draw operation if the view is not yet read.