“We are unable to process your request”

In the callback, I can see that the failure occurs on a .DS_Store file inside the folder. So for a .DS_Store, it is simple enough for me to just ignore the error and return COPYFILE_SKIP, but the somewhat more concerning issue here is that the true error reason is seemingly not reported? In the callback, if I read errno, it is 0. When copyfile returns, it returns -1 after I return COPYFILE_QUIT (and errno is 0), so I don't know what the error is or the appropriate way to handle it. FYI, the code to copyfile is actually open-source, so you can fairly easily find all of the places where your callback would have been called by looking for COPYFILE_ERR in the source. However: For .DS_Store, just skipping seems reasonable, but when copying a folder, it may be appropriate to get the true failure reason. ...I'd ignore all .DS_Store errors and, potentially, just skip copying them all together. The system will generate the file anytime it needs/wants to, and it's very likely that it won't consider the copied file vali

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. Albert Pascual
  Worldwide Developer Relations.

Thanks for the post, can you provide me the correct URL for the AASA file? the links above are not correct. If you prefer provide me this information in private. Go ahead and submit a code-level support request so we can discuss this further privately. When you create the request, indicate that you were referred by me at Apple and make sure to include a link to this thread. Thanks Albert Pascual
  Worldwide Developer Relations.

Hello - In order to resubmit your three IAP subscription products, the status of each needs to change from Developer Action Needed to Ready to Submit. We recommend editing each of them, in order to save an update (e.g.: add a note to the Review Notes section like [Date] Updating IAP to resubmit with new binary of Version 1.x of [App Name]. Once the status of the IAPs has been successfully updated, proceed to submit a new version of the app - and attach the three IAPs for review as documented here under Submit an In-App Purchase of the first time. If you are still unable to resubmit the IAPs with a new app build, please file a detailed ticket (including screenshots and/or video) via Feedback Assistant, and reply back to this thread with that ticket number - and we will follow-up. Thank you.

Thank you for your post and providing this information. I recommend using the direct line you have with Feedback Assistant to upload those files to the team working on your bug. Directly communicating with the appropriate team is always the most efficient approach. If you are unable to do so, I can assist you with the upload. Please let me know how you would like to proceed. Albert Pascual
  Worldwide Developer Relations.

Thanks for the backstory. [quote='880252022, shara7, /thread/818906?answerId=880252022#880252022, /profile/shara7'] which made me wonder whether this is a bug or intended behavior. [/quote] Well, it’s an an either or situation. Note this comment from the release notes: During the beta period, the cadence of notifications will be accelerated, enabling Apple and developers to address any issues that might occur. Honestly, I’m not sure whether this is what’s happening in your case or not. You might be able to learn more as to what’s actually going on by monitoring the system log entries from the ecosystemagent process. Many of these are at the debug level, so you’ll need to opt in to that. See Your Friend the System Log for hints and tips on using the system log effectively. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hi @Ziqiao Chen and everyone, Thank you for the follow-up. You were right to push for more precise testing — it led me to discover an issue with my original test setup and reach a much clearer understanding of the problem. == Correction: Original Test Setup == My initial frontmost test had a build configuration error: the test build still had an active HKWorkoutSession running in the background. This means the results I would have reported (~10 minutes before termination) did not reflect pure frontmost app state behavior. I've since corrected this and re-tested with precise instrumentation. == Hardware & Software == Apple Watch Series 8 (45mm) — not Series 4 watchOS 11.6.1 (latest stable) Build: Debug, standalone watch app Xcode debugger disconnected before all tests (to avoid priority elevation) == Methodology == I added a 30-second heartbeat timer that logs: Sequential counter and elapsed seconds Current heart rate value and time since last HR sample (hr_age_sec) App lifecycle transitions (ScenePhase ch

[quote='880412022, hasii2021, /thread/818406?answerId=880412022#880412022, /profile/hasii2021'] I put them [in FB22267132] but not sure if this is correct [/quote] That’s cool. When I open the system log snapshot you included (system_logs.logarchive) I see this: type: default time: 2026-03-17 21:32:51.951555 -0500 process: spctl subsystem: com.apple.securityd category: security_exception message: UNIX error exception: 2 type: default time: 2026-03-17 21:32:51.951587 -0500 process: spctl subsystem: com.apple.securityd category: security_exception message: MacOS error: -67068 type: default time: 2026-03-17 21:32:51.951603 -0500 process: spctl subsystem: com.apple.securityd category: security_exception message: MacOS error: -67071 type: default time: 2026-03-17 21:32:51.951615 -0500 process: spctl subsystem: com.apple.securityd category: security_exception message: MacOS error: -67071 This seems like an understandable error cascade: The first error, 2, is ENOENT, which is an e

Attaching the logs again: Filtering the log data using subsystem == com.apple.FSKit OR process CONTAINS[c] samplecode Timestamp Ty Process[PID:TID] 2026-03-17 15:15:51.832 I mount[16111:d88caa] [com.apple.FSKit:default] FSClient setting up connection to fskitd 2026-03-17 15:15:51.833 Db fskitd[589:d88a5f] [com.apple.FSKit:default] -[liveFilesMountServiceDelegate listener:shouldAcceptNewConnection:]: start 2026-03-17 15:15:51.833 Df fskitd[589:d88a5f] [com.apple.FSKit:default] Incomming connection, entitled 0 2026-03-17 15:15:51.833 Db fskitd[589:d88a5f] [com.apple.FSKit:default] -[liveFilesMountServiceDelegate listener:shouldAcceptNewConnection:]: accepting connection 2026-03-17 15:15:51.833 Df fskitd[589:d88a5f] [com.apple.FSKit:default] Hello FSClient! entitlement no 2026-03-17 15:15:51.834 Df mount[16111:d88caa] [com.apple.FSKit:default] Setting remote protocol to all XPC 2026-03-17 15:15:51.834 Df fskitd[589:d88a5f] [com.apple.FSKit:default] About to get current agent for 501 2026-03-17

@App Review Thank you for your response. We have not received any contact via App Store Connect so far. We have also submitted another support request through the contact form as suggested. We hope to hear from the review team soon. Thank you.

I am experiencing the same issue as last week too - I was able to sign apps this morning, now it stopped working. The team ID & everything stayed the same - but my iPhone complains that its Unable to Verify App. Is ppq.apple.com really up & running?

@DTS Engineer I have created fresh virtual machine with latest macOS, installed latest Xcode there and check. Behavior is still broken (check video below). https://drive.google.com/file/d/1THJ-o_4htaP2FvH8w4nt8IsbIsNefgZk/view?usp=sharing As you requested, I've also collected sysdiagnose: https://drive.google.com/file/d/1xv11WVYlVjCEVmggr37cETbqd-5w8Yyd/view?usp=sharing

Update: Still unable to locate the Purchases section under version 1.0.1 to attach the subscription. If anyone has a screenshot of where this appears in App Store Connect UI, that would be incredibly helpful. I dont know how to attach my subscriptions to the binary the UI element is not seen, thanks again