Search results for

“Apple Maps Guides”

155,875 results found

Post

Replies

Boosts

Views

Activity

Apple Developer enrollment stuck for a month — passport upload fails immediately in the app

I’m trying to complete my Apple Developer Program enrollment, and I’ve now been stuck in this process for about a month. The main issue is that the passport upload step in the Apple Developer app fails almost immediately every time with the same error, so I can’t complete identity verification and move forward. I’ve already gone through a very long back-and-forth with Apple Developer Support. At first, my enrollment through the website failed, and I was told to continue through the Apple Developer app instead. Then I ran into the passport upload issue in the app. Support asked me to upload identification documents through secure links, and I uploaded the requested documents, including my passport. I also updated my Apple Account name to match my official identification. During this process, one support representative, James, was helping me and there was a lot of back-and-forth. At one point it seemed like the case was being escalated and moving somewhere, but after

Developer Tools & Services Apple Developer Program Developer Program

11h

Reply to DMG notarization stuck In Progress 8+ hours — 12 submissions, all showing in-progress, not able to found any log related to any submission id.

Same issue, which is how I ended up here looking for answers. New app, 12+ hours. Sounds like need to just wait it out indefintely. I genuinely wish Apple provided some kind of update or logs when notarization was sitting in progress for such extended lengths of time.

Code Signing Notarization

12h

Production-Grade Implementation Guidance: DCError Matrices, Retry Strategies, and Simulator Testing for App Attest APIs

Hi there, We're implementing Apple's DeviceCheck App Attest for production iOS authentication. The public documentation defines DCError cases but doesn't specify which errors are expected per API method or recommend retry/remediation strategies. We need Apple's guidance to implement robust, production-aligned error handling before rollout. 1. Error Surface per API Method Question: Can you confirm the complete, officially expected set of DCError values for each method? We understand the following errors are possible across App Attest APIs: invalidKey invalidInput featureUnsupported serverUnavailable unknownSystemFailure Specifically, please confirm which errors can occur for: DCAppAttestService.generateKey() DCAppAttestService.attestKey(_:clientData:) DCAppAttestService.generateAssertion(keyID:clientData:) Are there any additional undocumented or edge-case errors we should handle? 2. Retry Strategy & Remediation Matrix Question: For each API method and error code, please help us with prop

Privacy & Security General App Attest

12h

Reply to Individual Enrollment Pending for 48+ Hours — No Response

Dear Apple Developer Support, I am following up on Case ID 30000003529740, submitted several days ago with no response. I purchased the Apple Developer Program (Individual, $99) on March 28, 2026 and received the Order Acknowledgement email. However, my account at developer.apple.com still displays Purchase your membership and I have not received any activation or follow-up communication. I also posted on the Apple Developer Forums but have not received a response there either. Could you please review my enrollment and let me know if any additional information or verification is needed from my side? I am happy to provide whatever is required. Case ID: 30000003529740 Thank you for your help.

Developer Tools & Services Apple Developer Program

12h

Reply to I have submitted my app and it has been waiting for review.

We submitted the application for review. Six days have passed and we are still waiting for the review process. Even applying for expedited review didn't help at all. How can we get the review result as soon as possible? This time, the review process for the application update is extremely long. After the last submission, the result would be given within 24 hours. We are loyal Apple developers and strictly followed Apple's review policies, hoping to get the result as soon as possible～～～～～

App Store Distribution & Marketing App Review

12h

Apple Engaged in Geographic Bias

We are a development team building an application targeted specifically for the Southeast Asian market. We have been caught in a frustrating review cycle and are hoping to get some guidance on how to move forward. The Situation Our application is intentionally unavailable in the United States. Per Apple's guidance, we implemented a We are currently not available in your country error screen that displays when a user's location falls outside our supported regions. This is intentional, expected behavior — not a bug. The Problem Despite providing detailed testing instructions and dedicated test accounts tied to the correct region, our Reviewers consistently: Do not use the test accounts we created for them Do not follow the regional setup instructions we provided Access the app from a US-based location See the geographic restriction screen (the one Apple instructed us to build) Flag it as a bug and reject the submission We have confirmed this is the root cause, as the rejection notes reference

App Store Distribution & Marketing App Review

13h

Reply to Is it possible to run both an NEPacketTunnelProvider and an NEDNSProxyProvider simultaneously?

It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. (Fortunately you @ mentioned me, otherwise I would’ve never seen this.) Do you know if it's still true that NEDNSProxyProvider is incompatible with Always-On VPN? This has not changed. When the Always On VPN [1] session activates, it specifically stops any existing sessions with the reason NEProviderStopReasonSuperceded. This includes sessions for normal VPN, Personal VPN, DNS proxy, and content filter. AFAICT this interaction isn’t documented in the Apple Platform Deployment guide, and I encourage you to file a bug against the doc to improve that. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Hmmm, sometime in the last 9 years Always On VPN lost its hyphen.

App & System Services Networking

13h

Reply to Digital Services Act Verification Stuck In Review (Turkey Address Documents Not Accepted)

Hello, I am experiencing the exact same issue. I submitted my compliance documents (also from Türkiye via e-Government) back on March 16th, and my status has been stuck in 'In Review' ever since. I have already opened a support ticket regarding this unusually long delay, but I am still waiting for a resolution. It seems like there might be a regional backlog or a specific review bottleneck for Turkish documents at the moment. You are definitely not alone in this! Please let me know if your status changes or if you get any feedback from Apple, and I will make sure to update here if mine gets approved. Hang in there!

App Store Distribution & Marketing App Store Connect

13h

My App stuck in "Waiting for Review" two week

Hello everyone, My app (ID: 6756186616) was submitted on Mar 15, 2026, and has been stuck in Waiting for Review status for over 17 days. I contacted Developer Support (case #20000111565861) and received confirmation that it's proceeding normally, but no update since. On average, Apple reviews 90 percent of apps within 24 hours. However, there might be cases that need more review time, but mine exceeds two week. Any recent experiences with long queues? Thanks!

App Store Distribution & Marketing App Review App Review

13h

Reply to Need MetricKit Implementation details for MacOS background Application, mainly for

Thanks for all the extra info. Just for the sake of debugging, I want to focus on this: [quote='882548022, PavanGulla, /thread/821002?answerId=882548022#882548022, /profile/PavanGulla'] Both didReceiveMetricPayloads: and didReceiveDiagnosticPayloads: are implemented [/quote] When an app crashes, MetricKit delivers the diagnostic playload immediately after the user relaunches the app. This is great way to test whether the basics are working: Start your app. Kill it from Terminal: % killall -ABRT Test821002 replacing Test821002 with the name of your app. Wait for the crash report window to show up, and then dismiss that. Relaunch the app. You should see the diagnostic payload delivered promptly. Please try this and let me know what happens. ps I realise that you’re primarily interested in metric payloads rather than diagnostic payloads. The purpose of this test is to confirm whether the basics are working. If they are, we can return to the metric payload issue. But if this diagnostic payload test fails, then we

Developer Tools & Services General

14h

Apple Developer Program renewal unresolved since July 10, 2021

Hello, I am requesting guidance regarding an unresolved Apple Developer Program renewal issue. My Individual membership expired on July 10, 2021. I previously submitted support requests, including Case #102854085591, but I still do not have a clear resolution as of April 1, 2026. Details: Team ID: C69P64A2ZN Membership type: Individual Expiration date: July 10, 2021 Previous case number: 102854085591 Could Apple please clarify: Whether this membership can still be renewed Whether any action is required from my side Whether I must re-enroll instead of renew Any guidance would be appreciated, as this has been blocking my development work for a long time. Thank you.

Developer Tools & Services Apple Developer Program Developer Program

14h

Subscription for Developer program

hi there, i installed the app and paid for developer program in 26 march 2026, today is 1st april 2026 but there's no acces and i cant see anything, there's no refund, i can't refund because it's apple's subscription, what is going on? support didn't answered my questions almost 3 days

Developer Tools & Services Apple Developer Program Developer Program

14h

Reply to Certificates valid if account is changed?

[quote='882440022, KenH-Rave, /thread/821074?answerId=882440022#882440022, /profile/KenH-Rave'] Directly to customers. [/quote] OK. So you’re signing your code with a Developer ID Application signing identity? And, if you have any installer packages, you sign those with a Developer ID Installer one? If so, I wouldn’t anticipate you hitting any problems with updating your Individual team to an Organization team. Developer ID signing identities are very stable. We don’t revoke them willy-nilly, because that would ‘break’ shipping products [1]. So your existing shipping code should continue to work. I’m not 100% whether the existing signing identities will continue to work for new code. I suspect they will. But even if that’s true, it’d make sense for you to generate new ones because your existing ones have your Individual team name embedded in them, and it’d be nicer if you they had your Organization team name instead. Note that you have to be careful when creating new Developer ID signing identities. I talk ab

Code Signing Certificates, Identifiers & Profiles

14h

Reply to NEAppProxyUDPFlow.writeDatagrams fails with "The datagram was too large" on macOS 15.x, macOS 26.x

Honestly, this is all a bit of a mystery |-: I’d like to make sure I understand this bit correctly: [quote='882421022, Leo_Nagano, /thread/820771?answerId=882421022#882421022, /profile/Leo_Nagano'] with this code I still consistently hit [/quote] So you see this every time? Or are there some cases where this works? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

App & System Services Networking

14h

Reply to Network Extension "Signature check failed" after archive with Developer ID — works in Xcode debug

If you use Apple Development signing for your day-to-day development, you can set up a reasonable debugging workflow. I explain how I do this in Debugging a Network Extension Provider. This still requires you to deactivate and then reactivate your sysex every time you change your code. That’s necessary because activating a sysex copies it from your app to a protected location on the file system, so without reactivation you end up running your old code. Debugging a Network Extension Provider discusses two key techniques for reducing the hassle associated with this process, namely: Unit tests Well-considered logging Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

App & System Services Networking

15h