Overview

When transferring photos from my iphone 16 Pro Max running the IOS 27 Developer Beta to a Windows 11 PC via a USB-C cable the photos convert to AAE files, which you can't preview of view.

Hi everyone, I'm experiencing a frustrating situation with my app and hoping someone from Apple or the community can help or has faced the same. Situation: I configured two auto-renewable subscriptions (premium_monthly and premium_yearly) in App Store Connect under a subscription group Submitted them for review along with a new app build The app build was reviewed, accepted, and is now live on the App Store The subscriptions have been in "In Review" status for 20+ days with no action Impact: In production, StoreKit does not return the subscription products at all (as expected — Apple doesn't serve unreviewed products to StoreKit) Users cannot purchase subscriptions Monetization is completely blocked for a live, approved app What I've already tried: Submitted an expedited review request — no response Submitted a new app version update to force a combined review — app was approved again but subscriptions remain "In Review" Contacted App Store Support via the online form — no response after multiple days Cannot edit or resubmit the subscriptions because they are locked while "In Review" Technical details: Using Flutter with the official in_app_purchase package (v3.2.0) Implementation verified correct — prices load fine in sandbox/simulator Existing lifetime non-consumable (remove_ads_premium) is approved and working in production Only the two new subscriptions are stuck Questions: Is there any way to escalate a stuck subscription review beyond the standard expedited review form? Can I delete the subscriptions while they are "In Review" and recreate them, or will that cause issues with product ID reuse? Has anyone else experienced this and found a resolution? Any help or guidance from Apple engineers or fellow developers would be greatly appreciated. Thanks

I would like to use the memory limit during interactive editing on iOS to decrease jetsam risk. However, I'm unsure of what to set it to. Do you have a recommendation as a fraction of physical memory? I have set the extended virtual memory entitlement, but I don't know what fraction of physical memory (or more) that entitlement enables - perhaps I should use a larger memory limit for M1-based iPads?

Which of the Vision framework‘s support for grounding/bounding boxes/segmentation carry over to the iOS 27 on-device Foundation Model image support?

The iPhone Lock Screen lets you display a small time and date at the top of the display that has a neat image processing effect where the text takes on the underlying colors with a blurred gradient while still maintaining legibility appearing largely white. In this screenshot you can see the white text features blue colors at the top left and transitions to a purple color on the right due to the underlying vibrant blue and purple blocks. Can you share how this text effect is achieved using Core Image?

In WWDC20 it was mentioned that missing compileTime/renderTime (or no intermediate image with the dump-intermediates option) can indicate a cached intermediate. I have also seen renderTime=cacheHit on passes that are clearly rendering intermediates, and an actual renderTime is only properly shown on the final pass which always seems to equal the final time render time. In compileTime it says cacheMiss. Which fields should be considered authoritative for tracking intermediate cache hits versus actual rendering? Thanks!

Are color differences expected for any cameras? I have heard some reports, but have not seen it myself. If it's not expected, then I can get those people to file bugs.

Is the memoryLimit option mentioned in WWDC26 session 305 the same option as CIContextOption.memoryTarget? The session says the default memory target on iOS is 256 MB. What is the default memoryTarget on macOS? Also, the session recommends the Extended Virtual Addressing entitlement for interactive RAW editing. That entitlement does not appear to be available for macOS, so does Core Image automatically use a larger intermediate cache budget on macOS? Should memoryTarget be used only for export contexts, or can/should it also be tuned for interactive editing contexts with cacheIntermediates enabled? Thanks!

I render images using a tiled/LOD pipeline. The final render usually requests only the visible ROI at the current display scale, which works well for local filters. The difficult case is filters that need a lower-resolution full-extent or larger-extent input, such as guided filters, blurs, histograms/statistics, and reduce passes. If that dependency remains inside the same CI graph, ROI propagation can force larger-extent evaluation of the upstream image, defeating small-ROI rendering. My current approach is to render those intermediates in a separate lower-resolution CI render pass, cache the result, and feed the rendered intermediate back into the final graph. Is this the recommended architecture, or is there a better Core Image structure for expressing this kind of intermediate render/cache barrier without manually creating and rendering a separate intermediate graph? Thanks!

Could you provide a more detailed description of how isHighlightRecoveryEnabled affects the image, and how it differs from isGamutMappingEnabled? I’d like to explain these controls accurately to my users. Does highlight recovery run before or after linearSpaceFilter, and should it be disabled when generating scene-referred linear output? Thanks!

Here are two additional RAW 9 bugs: Horizontal Line in RAW 9 decode: FB23076983 CIRAWFilter.scaleFactor not respected in RAW 9 for some RAW formats: FB23076984

CIRAWFilter documentation lists despeckleAmount as available on macOS 12.0+, but I cannot find this property in the macOS 26 headers. Could you provide a detailed description of how despeckleAmount affects the image so I can explain this adjustment accurately to my users? Does it run before or after linearSpaceFilter, and what should it be set to when generating scene-referred linear output? Thanks!

When processing RAW images with CIRAWFilter's extendedDynamicRange, does the boost filter’s behavior change? How does boost handle extended range values and does boost have a limit before clamping? Also, in the RAW EDR case, should we still use the linearSpace filter or is it now fine to run filters post-boost (assuming the filters are linear-dependent and can run post-boost)

In my testing, enabling isDraftModeEnabled improves decode performance for very large non-RAW images. Does it also affect decoding performance or quality for RAW images? Are there non-RAW formats that benefit more than others, or not at all, with draft mode? For non-RAW images, is it generally recommended to load them through CIRAWFilter or CIImage? If CIImage is preferred, is there an equivalent to isDraftModeEnabled for CIImage initialization? Conversely, if CIRAWFilter is acceptable for non-RAW images, how can I get the expandToHDR behavior that is available through CIImage options? Thanks!

I am trying to compress a CIImage below a certain file size threshold when creating a JPEG. Currently, I am handling this in, potentially, multiple passes. In the first pass, I am essentially calling:
encodeJPEG(CIImage, quality: 0.85, colorSpace: CIImage.colorSpace ?? CGColorSpace(name: CGColorSpace.sRGB)!)
I am then checking the image size. If the image is still too big, I try to estimate how much I need to reduce it and try again until the image size is small enough. My question: Is there a more efficient way of doing this?

What is the difference (if any) between RAW 9 and RAW 9.DNG in terms of quality, noise reduction, and color?

What is the minimum iPhone system requirement for RAW 9? Anything that can run iOS 27 / iPadOS 27 / macOS 27? I was getting some ANE errors on an M1 MacBook Air this morning (FB23103074)

I’m really excited about RAW 9, great work! Since RAW 9 is not enabled by default, are there any recommended use cases where it makes sense to select it by default, if supported? For compatibility handling, should I treat decoderVersion as covering all processing and adjustments performed by CIRAWFilter, or does it mostly affect the RAW decoding stage? When switching decoder versions, should I re-evaluate which CIRAWFilter adjustments are supported? Also, the macOS 26 headers appear to expose version9 and version9DNG. Is RAW 9 actually supported on macOS 26 runtimes? Thanks!

What is the high water mark for rendering an image in RAW 9 vs. RAW 8? I realize it depends on the megapixels of the render, but what can you share memory wise, especially compared to RAW 8, perhaps as a multiple? I'm mostly concerned about iOS in case that's relevant.

Hi everyone, I recently updated my Mac to macOS 27 Golden Gate Beta and have encountered a strange issue with window management over a remote connection. Issue: When connected to my Mac via Chrome Remote Desktop (CRD), I can no longer move application windows by dragging their title bars (outer frames). Details: Curiously, I can still drag and move individual tabs within apps (like Chrome or Terminal), which means mouse drag input itself is being transmitted correctly to the OS. This issue only happens when attempting to drag the window title bar/frame over a remote session. Local mouse/trackpad control works perfectly. Everything was working completely fine before the update to macOS 27 Golden Gate Beta. What I've tried so far (with no success): Toggled Accessibility permissions off and on for ChromeRemoteDesktopHost and restarted the Mac. Disallowed and re-allowed Screen Recording permissions. Completely re-installed the Chrome Remote Desktop host application. Disabled "Tile windows by dragging to screen edges" in System Settings to avoid snapping conflicts. It seems like WindowServer or the system-level window management is blocking or ignoring virtual mouse drag inputs specifically on title bars since this beta update. Has anyone else experienced this on macOS 27 Golden Gate Beta, or is there a known API change / security restriction in this version that affects remote input handling for WindowServer? Any insights or workarounds would be greatly appreciated. Thank you!