We are unable to process your request

I have the same issue. Since I am using the FoundationModels to process the user question, I cannot use AppEnum. The user experience where they have to first say Ask and then ask their question is bad. What's the solution in this case? I want it to be like Siri, ask chatGPT

Thank you for your post. We recommend that you sign up for a session with App Review during the weekly Meet with Apple event. Sign in with your Developer ID and select Request a one-on-one App Review consultation. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines.

We have observed a per-process limitation on the number of simultaneous nw_connection_t objects in certain macOS environments. On some systems, this limit does not appear to apply, but on others the limitation is reproducible. When a process attempts to establish a large number of connections (e.g. 512+), some connections enter the nw_connection_state_waiting state and report the POSIX error “Cannot allocate memory”. These connections remain stuck indefinitely, even after other connections are deallocated and resources should theoretically be available again. The answer here is basically, yes, you're hitting a limit (which is ~512). More specifically, if you look at the thread that's getting ENOMEM in the system console and trace that thread back into the kernel, I believe you'll find that you’re getting log messages similar to this coming from the kernel: kernel … SK[6]: flow_owner_flowadv_index_alloc nw_playground(44836) flow advisory table full: num 512 max 512 kernel … SK[6]: flow_entry_

Is there a supported way to clear per-app consent so the system prompts again? There is no supported way to achieve the desired functionality given the currently shipping system configurations. If you would like for Apple to consider adding support for such features, please submit your suggestion request via Feedback Assistant. For more information on Feedback Assistant, please visit https://developer.apple.com/bug-reporting. Under what conditions should the “Share Age Range Again” control appear in Settings, and is there an equivalent way to trigger it for testing? It appears prior to the anniversary of the original request, and when a user previously declined or a user has aged out of a current age range. Are there best practices for QA (e.g., using Ask First at the system level, testing on real devices vs. Simulator, using a separate bundle ID for dev builds, or other steps)? Testing in the Simulator is unsupported. If you use a separate bundle ID, the system treats it as a different app.

Part 2... That leads to here: and how can I make sure my app will be allowed to update when I need it too. The first thing I'd do here is shift the way you're thinking about this issue from how do I remove/bypass quarantine to how do I make sure my update process always works. You've focussed on quarantine because it's a fairly common edge case; however, the problem with focussing on solving it is: The system’s behavior is opaque and undocumented. This means, as you're already experiencing, it's hard to make this work right at all, and even if you succeed, it's very likely that something will change in the future, leaving you back with the same problem. Quarantine is only one failure source of many. For example, what if the actual problem is that the app is being run from a read-only location like a network share? That second point is what makes this problem so tricky. The full range of valid macOS configuration is so large that it's effectively impossible to fully test or predict. This means you end

Sorry for the late reply to this, it was outside of the areas Quinn and I normally monitor and we both missed it. In any case, some additional questions were passed over to me through a DTS ticket, so I'm going to answer your questions above and then the other questions that were passed to me. (Splitting posts for length) First of all, as a general comment here: I am looking for alternatives and was previously under the impression that if we were to move to a DMG then that would provide the user a better user experience for moving it. So, one thing to understand here is that the pattern of using disk images for software distribution is primarily a holdover of what is now ancient history, not technical merit. It started when software was being distributed on floppy disk as the easiest way to exactly duplicate the contents of the original floppy disk. Originally, these images couldn't even be mounted, so their only purpose was to be written back out to physical media. That pattern was then carried over to CDs a

Thank you for your post and the bug report that includes a focused sample to reproduce the issue. Your assistance is greatly appreciated. I recommend collaborating with engineering to resolve this matter as expeditiously as possible. You can see the status of your feedback in Feedback Assistant. There, you can track if the report is still being investigated, has a potential identifiable fix, or has been resolved in another way. The status appears beside the label Resolution. We're unable to share any updates on specific reports on the forums. For more details on when you'll see updates to your report, please see What to expect after submission. Thanks, Albert Pascual
  Worldwide Developer Relations.

If you haven't seen it yet, you should look over the questionnaire on the MapKit JS Capacity Increase Request form. — Ed Ford,  DTS Engineer

Now that this is mostly working, I've come across a new issue I'm wondering if anyone else is seeing. Using UTM version 4.7.4 on a macOS 26.0.1 host, I am setting up a macOS 26.1 beta 3 guest. I am unable to log into my Apple ID in the macOS 26.1 beta host. This happened with beta 1 and now with beta 3. This is not just the normal limitations of logging into an Apple ID in a macOS VM. With macOS 26.1 beta, you can't login at all. This means no iCloud access. This means you can't even update to the next beta since you need iCloud access for the Software Update screen to even offer the Beta Software update option. I also have a macOS 15.7.1 VM and a maCOS 14.6.1 VM on this same host and they both let me login just fine (with the usual limitations). I filed bug FB20668616 but I'm curious if anyone has seen this. One step forward, one step back.

We’re unable to use our custom photo picker either, because when the user denies full photo access, the system displays a dialog to select specific images. Unfortunately, touch input doesn’t work properly there either, making it impossible to select any images.