“We are unable to process your request”

Thank you for your post. I see that you have already submitted those files for the issue and appreciate your efforts. The team is currently experiencing high workloads and only communicates when a fix is released due to company policies. I can assure you that this issue is on the team’s priority list. It has been marked as an existing bug and will be addressed as soon as a fix is available. Once the fix is released, the team will notify you via Feedback Assistant to test the new release. I understand that the process can sometimes be slow, and this bug may have been present for a longer period than anticipated. Albert Pascual
  Worldwide Developer Relations.

Thanks for that, always hard to read XML as Xcode presents that pretty good. It looks completely clean and the com.apple.developer.associated-domains only contain keys that are allowed https://developer.apple.com/documentation/BundleResources/Entitlements/com.apple.developer.associated-domains Will be good to go over that: https://developer.apple.com/documentation/bundleresources/entitlements/com.apple.developer.associated-appclip-app-identifiers So the string should start with applinks: and the section for app domains should only contain the app clips: https://developer.apple.com/documentation/xcode/supporting-associated-domains. I'm going to post a way for us to connect and go over your project to review the project. Probably we will need to go over Xcode. I'd like you to 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. Albert Pascual
  W

@App Review Following up on your response from 2 days ago. Our app (Apple ID: 1505684382) has now been in Waiting for Review for 16 days — submitted March 4th. Despite your message that you would contact us via App Store Connect, we have received no communication there. To summarize what we have tried: 2x Expedited Review requests — no response 2x Support cases via Contact Us — no response This forum post — your team replied but no follow-through yet We have exhausted every available channel. Our app includes a time-sensitive subscription pricing test, and every day of delay is causing measurable revenue loss. We respectfully ask for a concrete answer: What is preventing our app from entering review, and when will it be reviewed? Thank you.

Thanks for providing that extra context. There are two ways that Apple can grant you access to managed entitlements, via an old process or a new process. I explain those processes in detail in Using the Multicast Networking Additional Capability (this is for a different entitlement, but you should recognise the processes). It seems that your teams are configured with a mix of the old and the new. For example, WEJZZZZZZZ is using the old process whereas NWKYYYYYYY is using the new process. I don’t have any insight into the old process setup, but I can see the setup for new process stuff and I’ve confirmed that NWKYYYYYYY is set up correctly. However, to use it you have to use the new process, rather than the old process. To learn more about this, read Account > Reference > Provisioning with capabilities. At the bottom of that page is a Migrating additional entitlements to capabilities section. This explains how you

Please try again after a restart. I went through this process myself and hit very similar symptoms. I found that fskitd had a bunch of threads stuck like this: 816 _dispatch_call_block_and_release + 32 (libdispatch.dylib + 7004) [0x19b4ceb5c] 816 ??? (fskitd + 132900) [0x100988724] 816 ??? (fskitd + 86796) [0x10097d30c] 816 ??? (fskitd + 87588) [0x10097d624] 816 ??? (fskitd + 50740) [0x100974634] 816 objc_sync_enter + 20 (libobjc.A.dylib + 70452) [0x19b245334] 816 816 __ulock_wait2 + 8 (libsystem_kernel.dylib + 60532) [0x19b656c74] *816 ??? (kernel.release.t6031 + 6477368) [0xfffffe0008ea1638] (blocked by turnstile waiting for fskitd [634] thread 0x30444d) Worse yet, the number of threads kept growing, every time I retried the mount command! I was able to clear this by restarting, after which the mount command worked as expected. I did some spelunking based on internal resources and it seems that these threads are deadlocked due to some previous error starting the extension. Hence my idea to restart

Submitted for code level support request , I have been stuck for more than two weeks now with no progress. I’ve raised multiple support tickets and posted on forums, but haven’t received any response Please let me know if there’s another way to reach your team or escalate this issue

Albert Pascual -- I am unable to send a code-level support request because I no longer have a paid developer account. Without going into grim detail, since I could no longer type very well after the accident, I had to leave my career as a developer. It sucked. I had been doing backend development back when there was a Mac OS X Server and an ADC membership was $500 a year. But being disabled as I am gave me a lot more appreciation for accessibility in macOS. Having these things working is important to my quality of life. Last night I installed 26.4 RC and there are multiple new issues. At this point I'm going to have to reset to 26.0 because too much of what I rely on either doesn't work or has become too irritating. A few examples: the orange dot in the upper right corner somehow became more distracting as it is now an orange square with a black border. Still just as useless but now extra annoying. Now when I say Hey Siri and my computer is locked, Siri responds with You will need to unlock

Which bit? I was unaware that I could simply run both mitmproxy as well as rvictl and tcpdump at the same time. However I did just that; inspecting the trace file (in Wireshark) revealed the following (bundle name redacted): [Process Information: com.apple.WebKit(1114) [(1111)]] [Id: 1114] [Name: com.apple.WebKit] But I guess you are right in that this does not tell me anything I did not already know. Furthermore I do not see any TLS handshake messages after the server sent its certificate along with the Finished message which confirms that there might be some sort of pinning going on.