Hi everyone, I’m facing an issue where my Apple ID still appears to be associated with a developer team even after being removed. Here’s the situation: I was part of a company Apple Developer Program team. I have already followed Apple’s official “Leave a Team” steps. I have also been removed from App Store Connect by the Account Holder. The Account Holder confirmed that my Apple ID is no longer visible under Users and Access However, when I log in to https://developer.apple.com/account, I can still see the team listed under my account. This seems like a mismatch between App Store Connect and the Apple Developer Portal. Has anyone else experienced this issue? If so: Did it resolve on its own after some time? Or did you have to contact Apple Developer Support to get it fixed? Any guidance would be really appreciated. Thanks in advance!

Hi, I’m looking for clarification on TN3134: Network Extension provider deployment, specifically iOS deployment requirements for: packet tunnel provider DNS proxy provider From the documentation: Packet Tunnel Provider App extension (min iOS 9.0): per-app mode requires a managed device DNS Proxy Provider App extension (min iOS 11.0): supervised devices only App extension (min iOS 11.0): per-app mode requires managed devices Issue I implemented a DNS proxy using NEDNSProxyManager. Works as expected in debug builds on a local device Fails to configure when distributed via TestFlight Console Output (TestFlight build) error 10:05:39.872258-0500 nehelper The production version of *** is not allowed to create DNS proxy configurations. Use MDM to create DNS Proxy configurations for the production version of ***. Question Is it possible to distribute a DNS proxy provider for use on non-MDM / non-supervised devices? If not: Is the limitation strictly enforced at distribution/runtime? Is a packet tunnel provider the only viable alternative for App Store distribution? There is a lot of different VPN apps on the App Store that appear to work out of the box without MDM or supervision, which suggests they are using a different deployment model. Thank you for any clarification or guidance!

We are facing a critical issue with our Apple Developer account that is currently blocking app releases. Context: Organization account (Apple Developer Program) Account Holder: Ben Kunkel Apple Business Manager integrated with Okta (SCIM) Issue: The original Account Holder was deleted from Apple Business Manager and re-created via SCIM The recreated account now shows as “Staff” (Source: Custom Sync) and cannot be modified In Apple Developer, Ben is still listed as Account Holder but does not see any options to accept agreements or manage the account A transfer request was initiated to me before he left the company, but I am unable to complete identity verification (“Invalid Submission” error) Result: No active Account Holder can take action Unable to accept the updated Apple Developer Program License Agreement App submissions and updates are blocked (production impact) This appears to be a cross-system identity mismatch between Apple Business Manager and Apple Developer due to SCIM provisioning. Has anyone faced a similar issue? Any guidance on resolving this or getting it escalated internally would be greatly appreciated. We already have open cases with Apple Support, but progress has been slow. Thanks in advance.

I enrolled in the Apple Developer Program about 7 days ago, but my account is still showing as “Pending,” and I haven’t received any updates yet. I’ve already contacted Apple Developer Support via email, but I haven’t heard back so far. I wanted to check if this waiting period is typical, or if I should take any additional steps to complete the enrollment process. Has anyone experienced a similar delay recently? Any guidance on the usual approval timeline would be appreciated.

Hello, I'm working in the team with 70 i(Pad)OS test devices running 24/7, and 40 of them are iOS 18 or 26. The problem is: for enterprise apps to be tested (signed with ADEP inhouse profile) the devices over iOS 18 require Enterprise App developers to be allowed at least once with physical control on-device after reboot, which is quite burdensome because we put all the devices in the restricted area, supposed to be used from the remote. Devices are logged into Apple ID for the prevention of Activation Lock but no preparation nor management via MDM over Apple Configurator 2. Is there any binary, tool, app that can check (letting us allow devices for those developers would be even better) if the Enterprise App developer(s) are allowed for the device via terminal or VNC?

Hello everyone, I’m posting here to see if someone from the Apple team or the community could help or provide guidance regarding my Apple Developer Program enrollment. My name is Bruno, and I represent 2B Digital LLC. I submitted my enrollment on February 15, under Application ID: 946JTL58KD, with the intention of developing and distributing iOS applications. Since then, my application has remained under review, and unfortunately I have not received any response so far. I also opened a support ticket but have not received any reply there either. At this point, I would really appreciate any update regarding the status of my enrollment or guidance on what steps I should take next. Thank you in advance for any help.

Hey everyone, I applied for the App Store Small Business Program on February 18th and I still haven't heard anything back, that's almost 20 days now. Is this normal? How long did it take for those of you who got approved? I'm starting to wonder if my application even went through correctly. Would really appreciate hearing your experiences — especially if you applied recently. Did anyone else wait this long? Thanks

I’m looking for advice from anyone who has gone through the process of converting an Apple Developer account to an Organization / Company account. I’ve been trying to convert my account for organization and the process has been taking much longer than expected. Apple initially requested documentation to verify both the business and my authority to act on behalf of the company. So far, I have already provided or prepared everything they ask for. At this point, I’ve been waiting for 9 days without much clarity on whether my documents are sufficient

We are experiencing an issue with ADCertificate auto-renewal on macOS devices enrolled via MDM. Platform: macOS CA: Microsoft AD CS Payload Type: com.apple.ADCertificate.managed Initial certificate enrollment works correctly EnableAutoRenewal is set to true Certificate does not renew automatically as it approaches expiry We would like to confirm: Are there any known issues with macOS ADCertificate managed payload auto-renewal, particularly with Microsoft AD CS environments? Below is the exact payload configuration in use: Thank you.

Hi everyone, I’m seeking some advice on a recurring rejection for our app, tassie., regarding Guideline 3.1.1 (In-App Purchase). The Situation: Our app offers walking tours. While we sell public tours via In-App Purchases (which works perfectly), we also create bespoke, private tours for corporate clients (e.g., a specific company teambuilding event or a private anniversary tour). These tours contain company-specific info and are not available for sale to the general public. The Issue: We use "Partner Codes" (Access Codes) to allow employees of these companies to unlock their private tours. Apple keeps rejecting us under 3.1.1, claiming we are bypassing the IAP system. Our Argument: We believe this falls under Guideline 3.1.3(c) (Enterprise Users). The content is bespoke and created for a specific organization. The end-user (the employee) does not pay for this content; it is a B2B transaction between us and the corporation. The content is not relevant to the general public and therefore not suitable for the public IAP storefront. The Question: Has anyone successfully navigated this? We’ve tried explaining the B2B nature in the App Review notes, but the reviewers seem to hit a wall as soon as they see an "input field" for a code. Should we move the "Partner Code" field deeper into the Profile/Settings to distance it from the Shop? Is there a specific way to document the "Bespoke" nature of the content to satisfy the reviewers? Would an Appeal be the best route, or should we request a phone call (which we are currently scheduled for)? Any insights or experiences with Guideline 3.1.3(c) would be greatly appreciated! Thanks in advance, Danique | tassie.

Hello everyone, I enrolled in the Apple Developer Program on February 19th through the Apple Developer App. I completed my payment using mobile carrier billing and successfully uploaded my ID documents for identity verification. However, my account status is still showing as "Pending". I opened a support ticket regarding this issue on February 21st, but I haven't received any response yet. Since it has been 5 days and I am eager to proceed with my work, I wanted to ask if this delay is normal for carrier billing enrollments? Is there any additional step I need to take, or a way to expedite this manual review process? Any advice or help from the community or Apple staff would be greatly appreciated. Thanks!

I want to know about the time it takes to transition from an individual to an organization with Apple's Developer Program. I received an email notifying me that the transition process would begin on February 2nd, 2026, and today, February 19th, 2026, everything still shows as being in progress without any changes. So I want to know the maximum timeframe or how to know if they are actually completing this process. I have sent two support emails, but received no response.

Hi Apple Team, My enrollment ID is 78BT4GJN7C, enrolled at 5th Jan, till today is still "IN PROGRESS". Could you please give me some feedback when the enrollment would be completed?? Or, what should I do to accelerating the progress? Sincerely, Jim

Hi Team, Its been 4 weeks and still my enrollment is reflecting in pending status. I want to set up my application and to do it we have to enroll for the development to give access to the the tech team to configure the application. I am not able to find the contact us info to raise the issue.

Hi, I tried to sign up for the Developer Program 7 times, starting on January 5th. It's now been a month. I contacted customer support, they said to try enrolling through the Apple Developer App. I tried that, it asked me to do an identity verification, which I did, successfully. Then the "enroll" button on the app got grayed out and it says: "Enrollment through the Apple Developer app is not available for this Apple Account. Visit http:// developer.apple.com/programs/enroll/." I go to that link, I click "continue with your enrollment", I pay the $99, it goes through, I don't get charged anything, just a $0.00 authorization transaction, then get the "Order Acknowledgment" email, then nothing happens, it just goes nowhere. Please help. If there is anything I can do, or any more information I should supply for this to go through. I contacted support multiple times, but I don't get any response. My enrollment ID is DPTB3R8T2Z.

Hi everyone, With the rapid growth of digital banking, payments, and AI-driven financial services, building secure and scalable FinTech apps on iOS has become more complex than ever. From handling sensitive user data to ensuring compliance and seamless performance, iOS developers face multiple technical challenges. Key areas that usually require deep expertise include: Apple Pay and Wallet integrations Secure authentication (Face ID / Touch ID / biometrics) Real-time transaction processing Core ML for financial predictions SwiftUI dashboards for financial analytics Data encryption and regulatory compliance https://www.nimbleappgenie.com At Nimble AppGenie, we’ve worked extensively as a FinTech app development expert, helping startups and enterprises design and build iOS financial applications that are secure, scalable, and user-centric. Our experience shows that the most successful fintech apps are those that balance strong security architecture with intuitive UX and performance optimization. I’m interested to hear from the community: What are the biggest challenges you’ve faced while building fintech apps on iOS? Are there any recent iOS updates or Apple frameworks that significantly improved your fintech workflows? How are you handling compliance and security in production apps? Looking forward to learning from everyone’s experiences and best practices.

I'm having issues accepting an invite to access TestFlight. I may have tried multiple attempts due to my existing email address not being accepted, so I had to create a new email that's not linked to Apple yet and put it in the activation form. However, now I am getting an error, "Verification codes can't be sent to this phone number at this time. Please try again later." This has been an error since yesterday and the resend, verification via call, and text are all not working. I also tried a different phone number and same issue. Can someone help on this, please.

{ "logFormatVersion": 1, "jobId": "e2ec4d13-bb83-41d4-a497-ba80cf830af1", "status": "Rejected", "statusSummary": "Team is not yet configured for notarization. Please contact Developer Programs Support at developer.apple.com under the topic Development and Technical / Other Development or Technical Questions.", "statusCode": 7000, "archiveFilename": "Lens.zip", "uploadDate": "2026-01-23T16:13:37.589Z", "sha256": "fd52815d5edf14b66b25529e89c207b2acff2c41642261e1049a479f19f2b72f", "ticketContents": null, "issues": null }} I am getting this error and have opened a support ticket for 3months so far and neither the development team or engineering team has replied as to why our development account has been BLOCKED. We just signed up, and are a legal entity in delaware. To other developers, how have you proceeded with such issues?

We operate a native iOS app that authenticates users via the system browser using OIDC against a 3rd party SaaS authentication broker, which then performs authentication against the individual customer IdPs using SAML within the browser session, and then completes the OIDC login between the broker and our application. Our application initiates the OIDC login using ASWebAuthenticationSession, using the broker’s library, against the broker, and at that point the authentication workflow is handled by the broker. At the beginning of the login session, the broker sets a session-identifying cookie for their domain, before redirecting the user to their company’s identity provider to authenticate, which then redirects the user back to the broker. Intermittently, Mobile Safari does not include that previously set cookie on the final communication with the broker, when being redirected from the IdP as the final step of the SAML portion of the login workflow. When the cookie is missing, the broker cannot correlate the authentication response to the original request and the login fails, even though the user successfully authenticated at their identity provider. The same user can sometimes find success after retrying on the same device minutes later, without any changes. When we first started diagnosing this issue, we were seeing about a 20% rate of these errors across all Mobile Safari logins, which we can identify fairly conclusively (from provider logs, based on their guidance) as being caused by the session cookie set in one request not being provided on the subsequent request to the same domain. Our authentication broker provider has indicated, based on their server logs, and logs from an affected device, that this behavior is caused by Mobile Safari’s Intelligent Tracking Protection (ITP) causing Mobile Safari to not send the login session cookie to the broker when handling the SAML redirect from the IdP back to them. Our authentication broker provider recommended that we switch the SAML Request binding setting from POST to Redirect in the SAML configurations against our customer IdPs, which reduced the rate of these errors to about 5% for most of our customers. However, we have at least one customer which is still seeing about a 20% rate in these errors for Mobile Safari logins after this change, and even a 5% error rate seems high. Our authentication broker has not been able to suggest any further remediation options, and has suggested we contact Apple for assistance. Our questions are: Is it reasonable to assume that ITP is causing this issue? Is there any way to confirm, conclusively, that ITP has caused a previously-set cookie to not be provided on a subsequent request to the same domain, i.e. via device logs? If so, are there any steps which can be taken to reduce or eliminate this error? Changes to how ASWebAuthenticationSession is invoked? Changes to the Authentication Broker which would reduce the chance of ITP being triggered? Changes to the Customer IdP configuration which would reduce the chance of ITP being triggered?

Hello All, I come to ask a question that I haven't been able to find the docs. I continue to work on implementing declarative management and while working there is a question/concern I have. I have noticed that during some destructive testing, if the device is attempting to fetch a configuration and the server responds with a 503 (or any server related error) then the device will wipe all configurations and attempt to reapply them. Is there any way to prevent this by intercepting status codes or would the only real solution be to force down a temp/test config if the real config can't be fetched from the server?