Also seeing this issue in our apps. Thanks for the swift response and the workaround. Hopefully, this will be fixed in beta 5. 🤞

Thanks for the response, J0hn! Btw, did you find a solution for the import use case (as we discussed in this thead)?

Good to hear that I'm not alone. I also tried the generic .system.open, but no external data is passed to my app. 🤷‍♂️

Thanks! I reached out twice (102888358215 & 102895781178). App Review is supposed to call me in the next few days. But I'm honestly not sure how much they can do. It seems to be a technical issue with the review environment. I'm glad you are looking into this!

Thanks for looking into this, Quinn! Feedback is filed under FB22188848.

How did you write your kernels before? In CI Kernel Language? If so, I would highly recommend to not mix Metal and CIKL kernels in one rendering. It's best if you can translate all your kernels to Metal.

Good question. I would recommend to use the startTask(...) APIs of CIContext to render to a CIRenderDestionation. You get a CIRenderTask object back, on which you can call waitUntilCompleted() to get a CIRenderInfo object. When you Quick Look that in Xcode (mark the variable and press space), you get a very detailed render graph that, among many other useful info, shows how much memory the render pass required.

Hmm, this looks to me like a problem with profiling itself. If you run the experiment just in Xcode and watch the memory graph, you'll see that memory will return to normal a little while after rendering. Even if spamming the button, memory stays well within the resource limits. I don't know why, when profiling with instruments, those small 4 MiB surfaces don't get released. 🤷‍♂️

I can confirm what @ihomway says: it works after a reboot. 👍

It's still not working. Do we need to remove the previous toolchain download somehow?

But shouldn't the stack trace be longer in this case?

When you call CIRAWFilter(imageURL: rawURL, options: [:]) you are calling the old, deprecated CIFilter RAW API. What happens if you just use CIRAWFilter(imageURL: rawURL) (the actual initializer of CIRAWFilter)?

How does the crash look like? Where does it crash? Do you have a crash log?

Deferred here means that it's doing the bulk of the work later, but gives you something you can use and show the user quickly. So you can quickly show a preview of the capture (the 12 MP image) and a few seconds later update it with the fully processed 48 MP image. Since you want to use CIRawFilter, I'm afraid you have to wait for the full image to arrive before you can present the user with editing controls. But you can use the smaller image to bridge the UI transition.

All I did was to set the system & Siri language to English (US) and log in with a US sandbox account under Media & Purchases. Then I could enable Apple Intelligence on my iPad in Germany.