“Apple Maps Guides”

[quote='884395022, kpatel1991, /thread/821961?answerId=884395022#884395022, /profile/kpatel1991'] we have re-applied for the capability however upon submitting the form we got a Server 500 error. [/quote] Well, that’s not good. I reported this to the relevant folks, and they’re investigating. My understanding is that this error is coming from the redirect that happens after the request was submitted, so your request actually did make it into the system. [quote='884518022, ltanh, /thread/821961?answerId=884518022#884518022, /profile/ltanh'] When requesting Contactless Pass Provisioning for Enterprise Org, we can request the SharableCredential only. [/quote] My understanding is that you should use the current submission form, which requests the new capability, but you’ll been assigned the old capability until this issue is resolved. [quote='884518022, ltanh, /thread/821961?answerId=884518022#884518022, /profile/ltanh'] Do you have any ETA for the fix? [/quote] No. I can’t talk about The Future™ [1]. [quote='884

[quote='822750021, yonator, /thread/822750, /profile/yonator'] it seems like all of our libraries [/quote] These are static libraries, right? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

To what end? Most folks who ask questions like this are trying to do some sort of security product, in which case Endpoint Security is the right option. So I’m curious what you plan to do with this information if you’re not a security product. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for starting a new thread for this. I’ve seen reports of problems like this from others, so I’m currently researching how that panned out and I’ll reply with an update when I know more. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='822733021, Kesava_jawaharlal_fp1, /thread/822733, /profile/Kesava_jawaharlal_fp1'] We are building a VPN using NEPacketTunnelProvider where the intent is to route HTTP/S traffic through a local proxy server [/quote] To what end? My experience is that most folks on this path are trying to implement a content filter on iOS. We don’t support the use of packet tunnel provider for that. See TN3120 Expected use cases for Network Extension packet tunnel providers. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I don’t have a lot of insight into this — UI frameworks aren’t really my thing — but M78 posted their bug number (FB18243622) upthread, and from that I was able to see this is reported as fixed in Logic Pro 12.0. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

We understand your concern. It's important to ensure that your app is respectful and appropriate for all users and for that you should check the App Store policy and guidelines. https://developer.apple.com/app-store/review/guidelines/ https://developer.apple.com/app-store/guidelines/ https://www.apple.com/legal/privacy/data/en/app-store/ I would also 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. https://developer.apple.com/events/view/upcoming-events Albert  WWDR

Thank you for providing such a detailed account of the iCloud Drive file upload deadlock issue on macOS 26.4.1. It sounds like you've done extensive troubleshooting and analysis to identify the root cause. Here's a summary of what you've discovered and some additional thoughts or suggestions that might help refine your approach or assist others experiencing similar issues: Summary of Findings: Root Cause: A stale HTTP/3 (QUIC) session in nsurlsessiond's BackgroundConnectionPool leads to a deadlock during file uploads. Behavior: Deadlock occurs specifically with HTTP/3, while HTTP/1.1 works without issues post-restart. Affects larger files (>100 KB); smaller files may occasionally succeed. Restarting both cloudd and nsurlsessiond resolves the issue temporarily by clearing the poisoned session. Reproduction: Consistent behavior observed across multiple tests with varied file sizes. Diagnosis: Log analysis can help identify occurrences using specific grep patterns. Recovery: A targeted kill command for user-l