My Apple Developer account was recently terminated, and I received an email stating that the reason was section 3.2(f) of the Apple Developer Program License Agreement. However, I have not changed anything recently in our apps, business model, or developer activity, and I genuinely do not understand the reason behind this termination. I have always tried to follow Apple’s guidelines carefully and act in good faith. This termination has severely impacted my work and users, and I am urgently requesting clarification regarding what exactly triggered this action. If someone from Apple or the App Review / Developer Relations team could please contact me or review the case again, I would greatly appreciate it. Thank you.

Hi everyone, I’m trying to enroll in the Apple Developer Program as an Individual developer in Canada. However, when I try to complete the enrollment, I receive this message: “For one or more reasons, your enrollment in the Apple Developer Program could not be completed.” I have already checked my Apple Account information, including my legal name, country/region, phone number, billing address, payment method, and two-factor authentication. I also tried contacting Apple Developer Support, but I have not received a clear solution yet. Has anyone experienced this issue before? Any advice would be greatly appreciated. Thank you.

I'm currently experiencing the same problem that many have had with error 422 "Beta contract is missing." I read that I should contact Apple support, but when I try to access the support page and log in with my credentials, the page doesn't load and I can't generate a ticket to resolve this problem. I get the message "There was an error processing your request. Please try again later." And when I inspect with Safari it shows me this information: "errors" : [ { "id" : "9be0314c-3bd5-4143-a625-602322d7156e", "status" : "422", "code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title" : "Beta contract is missing for the app.", "detail" : "Beta Contract is missing." } ] This is when I want to share the most recent build of my app with external groups through Testflight, but additionally, when my internal testers try to access it through Testflight app, it shows the error "The requested app is not available or doesn't exist." Could someone tell me what process I should follow or where I can correctly generate the ticket for my error? Since the Apple support page does not load. Thanks!

When I query, an existing database with over 10,000 records from an Objective C app (i.e. CKQueryOperation) I get only N x 100 records returned where N varies each time between 0 and about 10 (i.e. never more than 1000 records and always an even multiple of 100). When I do a “Query Records” on the CloudKit Dashboard I get a similar number of pages of records downloaded (i.e. 0-10). If I tap “Query Records” multiple times I will get more pages of records until the full 10,000 are downloaded. This had been working fine until recently, both from the app and the Dashboard. There are multiple Record Types in the database. Only one Record Type is erroring. The other Record Types continue to work both from the app and the Dashboard. In particular, the Users Record Type has many many records and they all download to many pages with a single tap of “Query Records”. I have posted this to the Feedback Assistant under FB22358865. Here is my code: NSPredicate *predicate =[NSPredicate predicateWithFormat:@"modificationDate>%@",dateLastSynched]; CKRecordType theRecordName=[NSString stringWithString:@"Notices”]; // I also try this for @“Links” and @“Messages” and @“EventMessages" CKQuery *query = [[CKQuery alloc] initWithRecordType:theRecordName predicate:predicate]; CKQueryOperation *theOperation=[[CKQueryOperation alloc] initWithQuery:query]; [self startAQueryOperation:(CKQueryOperation *)theOperation theName:(NSString *)recordName]; -(void)startAQueryOperation:(CKQueryOperation *)theOperation theName:(NSString *)recordName{ theOperation.recordFetchedBlock=^(CKRecord *theRecord){ NSLog(@"XXXjust downloaded a %@",recordName); }; theOperation.queryCompletionBlock=^(CKQueryCursor *theCursor, NSError *error){ if(error){ NSLog(@"XXXerror %@",error); } if(theCursor){ CKQueryOperation *anotherOperation=[[CKQueryOperation alloc] initWithCursor:theCursor]; [self startAQueryOperation:anotherOperation theName:recordName]; } }; CKDatabase *publicDatabase = [[CKContainer defaultContainer] publicCloudDatabase]; [publicDatabase addOperation:theOperation]; } When I run this code in the app I get no “XXXerror” from the NSLogs. I get the expected number of “XXXjust downloaded a” EventMessages (435) and Messages (594) and Links (15) but I get varying amounts, 100 or 400 or 500 “xxjust downloaded a” for the Notices when I should get 10,118 records. Thinking that 10,000 records is too much, if I alter “dateLastSynched” for Notices I still get only 100 or 200, not the expected number. Note that the number is always a multiple of 100. This seems to be consistent with the typical number of records I get on the CloudKit dashboard each time I tap “Query Records”.

I inherit from a protocol that implements in its extension those functions, that should not be required by the adopting class and instead I get those errors. Could someone explain why those errors appear and how to fix it.

I am very disappointed and got no help/solution from Apple development team after many rounds of email communication and calls. Two months ago, I went through the process in apple developer website and purchased a developer account and received order acknowledging email from apple team, it said it will take 2 working days for process, however, there is no news after half a month, so I send email for enquires, and about two weeks later, I received the support reply that I should try to apply the account through "developer app" and I follow his guide to continue the workflow, however, I cannot submit my ID through the APP and prompted "error". Few days later, the developer web prompts "Your enrollment could not be completed" Then I sent several emails to developer support and got no response, finally, I call the developer support several times that they cannot explain the reason why my application is getting stuck somewhere and cannot provide the solution/alternatives. I hope someone here or apple developer team can review my case and provide the guide for me to proceed the account application. Thanks a lot My case ID: 102855764543

Hey everyone. This is probably the last straw I am trying to pull since I tried almost everything else. I have applied for the Apple Developer Program and the whole process started at the end of 2024. I got rejected the first time because Apple could not charge my card. It was clearly shown that the cost is $99, however, it was 106.65 Euros (I created a Revolut card with the $100 because I don't trust placing my card everywhere). I started the new process but this time I knew about the amount issue so I placed 150 Euros just to be safe. Automatic rejection with robotic AI response: "For one or more reasons, your enrollment in the Apple Developer Program couldn't be completed. We can't continue with your enrollment at this time." When I raised ticket about it I got no replies. Than both my friend and wife tried to apply for the program. Both rejected with the exact same messaging. I created a new Apple ID, new card, new everything and did everything "by the book". Again. Rejection with the same exact messaging: For one or more reasons, your enrollment in the Apple Developer Program couldn't be completed. We can't continue with your enrollment at this time... Can someone from Apple please tell me what are those reasons? I have been an Apple user for almost 10 years now. I was buying Apps from store. I am using iCloud+. Modest Citizen as some would say. What's the problem? How can I finally get to Apple Developer Program without being rejected by AI or some poor auto system?

Hi. I'm not sure if that's normal, but I'm waiting for the approval of the Developer Account today, already it's the 6th day. But not only waiting time confusing me. When I'm opening the account, it says that I need to process enrollment and wait 48 even considering that the payment was issued 6 days ago.

I set up all the App Store details, including support info and other required information, but I’m having an issue when adding a build and trying to save. The Save button turns red, and I’m not sure why. It’s not showing what I’m missing in the setup.

Hello! Every time I attempt to enroll into the program I get hit with one of the following two errors: Unknown Error Please try again. Apple ID Issue The region of the Apple ID that's signed in to Settings or System Preferences is different than the region of the Apple ID with which you signed into the Apple Developer app. Sign in to Settings or System Preferences with an Apple ID that has the same region. I’m very confused by this message because I have never changed the region of my Apple ID - it should be United States. How can I complete my enrollment?

EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid)) Crash Report

When implementing a custom right in macOS authorizationdb, the mechanism array element builtin:authenticate is displaying the message 'Enter the name and password of a user in the "(null)" group to allow this.' on the macOS credential prompt UI popup. I am trying to find a fix to avoid the reference to null group in the message label that is displayed just above the username and password input fields. The current plist uses class as the key and value as the evaluate-mechanisms. The mechanisms array includes mechanism array with elements "builtin:login-begin", "mycustombundle:mycustompreaction", "builtin:authenticate", "mycustombundle:mycustommechanism". I have tried specifying group in the plist, have tried setting hint in the MechanismInvoke for group, username, security, authority, prompt, reason among several other hints into the context duing the execution of mycustombundle:mycustompreaction, but none seem to fix the "(null)" in the message label. Any help is greately appreciated. There is not much of any documentation for developers implementing custom authorization in macOS.

I'm experiencing a persistent issue where my app uploads successfully to TestFlight and appears in App Store Connect, but internal testers (including myself) receive the following error when attempting to install: "Could not install xxxxxxxxx. The requested app is not available or doesn't exist." What works: The build archives and exports successfully via Xcode (local build, Release configuration) The IPA uploads to App Store Connect without errors via eas submit The build appears in TestFlight and passes processing I can add the build to my Internal Testing group Testers receive the TestFlight notification and can see the app What fails: When any tester taps "Install" or "Update," the download begins briefly, then fails with the "not available or doesn't exist" error This affects all internal testers on the account, not just one device Troubleshooting already completed: Verified code signing is correct: Release configuration uses CODE_SIGN_STYLE = Manual, CODE_SIGN_IDENTITY = "iPhone Distribution", with a valid App Store distribution provisioning profile (UUID: 39bc4c63-bc64-403a-a2a6-6737b3d33115) 2. Distribution certificate is valid: Serial 4838CD7571DE5361B98A5FB2F769F74D, not expired (expires 2027-04-16) 3. Regenerated provisioning profile via EAS credentials, removed stale profiles, and rebuilt — same result 4. Incremented build numbers correctly across multiple submissions (3004 → 3005 → 3006) 5. Previously resolved a signing misconfiguration (build 3005 was incorrectly signed with "Apple Development" instead of "iPhone Distribution" due to expo prebuild reverting settings) — this was corrected for build 3006, but the install error persists 6. Confirmed the build is not stuck in processing — it shows as ready for testing in App Store Connect 7. Tested on multiple devices running current iOS versions 8. Cleared TestFlight app cache and reinstalled TestFlight on test devices Why I believe this is a server-side issue: Multiple developers in the Apple Developer Forums have reported the identical symptom — valid builds that upload and process correctly but fail to install with this exact error message. In those cases, Apple Support resolved the issue on their end within 48 hours with no action required from the developer. The signing, provisioning, and build configuration were not the cause. This one is very specific to what I am dealing with https://developer.apple.com/forums/thread/778597 One developer stated you fixed it on your side, without any real reasoning which also leads me to believe this is not something I can fix on my end https://developer.apple.com/forums/thread/778597?answerId=884241022#884241022 I've exhausted all client-side troubleshooting and believe this may require intervention on Apple's side. Has anyone been able to fix this on their end and not only when App Development called? I went through tons of the feedback and tried it all and it doesn't seem to be fixed. It's been a month or so like this. I can't get any info on who to call. I sent in a report to feedback assistant and through app developer support

FB19249805 Main: The option to open files in New Window Tab doesn't appear anywhere in either Preferences or the contextual menu on clicking the files in the project (unlike previous Xcode versions). Only the option to open in New Tab is available (which is useless). This BREAKS EXISTING WORKFLOWS that have been established through years for countless developers. I can only see the option to open in New Tab, which breaks all existing workflows and habits. This results in an astonishing blow to productivity. Dear Xcode team: Please restore this option immediately! Additional details: Several years ago (I've been using Xcode since version 2), Xcode renamed the normal tabs into "Window Tabs" and introduced new "Tabs". The new "Tabs" proved to be a useless and counterproductive option for the following reasons: -They cannot be used in Behaviors. (Only Window Tabs can be, and many workflows have been built around this.) -It takes much longer to load a file into a Tab than into a Window Tab (where files are loaded nearly instantly). -Navigators and Inspectors cannot be customized for individual Tabs (only for Window Tabs). -Using both Tabs and Window Tabs is not an option, as it adds another tab bar that eats an enormous part of screen real estate without providing any benefits. Fortunately, we didn't have to use Tabs and could just disable them into oblivion where they belong. Now, in Xcode 26, the option to open files in new Window Tabs is gone. Really, I can only classify it as intentional sabotage. Many years of my Xcode habits and workflows are based on opening files in New Window Tabs via the Preferences > Navigation > With Option option. Or via the contextual menu. Now this option is gone. I'm sure there are plenty of other developers in the same situation. Please reenable the option to open in New Window Tabs. Thank you for your attention to this matter!

Hello, I recently applied for enrollment in the Apple Developer Program, and my application has been under review for some time (5 days now). I would appreciate any guidance or insight into the status or typical processing time. Here are my details: Full Name: Kingsley Ibok Enrollment ID: FX678S24XD Please what steps can I take now, I’d really appreciate Thank you.

My enrolment is pending since 13 April and I haven't heard from Apple yet. I have requested for call backs and sent emails. How long does it generally take to get enrolled?

When I use Xcode 26 (0.1, 1) for debugging and hit a breakpoint, using "step over" causes the debugger to freeze at a random line of code. Clicking "Pause program execution" indicates that the line is being executed, but the breakpoint never exits, seemingly causing a freeze. The application on the simulator also becomes unresponsive. However, when I do not use breakpoints, my program runs smoothly, and debugging on a physical device does not cause any freezes. This issue only occurs with the simulator. I am using Xcode on Apple Silicon, and due to some third-party SDKs that depend on Rosetta, our app can only run on the Rosetta simulator. We did not encounter this issue when using Xcode 16.x for simulator debugging. The current situation with Xcode 26.x significantly reduces our development efficiency. What could be causing this, and is there a solution?

Hi. On my iOS app, both the app store and the device are making changes to my app icon to make it look more Liquid-Glass. See attached image showing my original icon, and then how it appears on the app store and on devices. There is an added bevel/3d effect. I'd like to not have this happen. Did anybody figure out how to turn this off? So that the icon appears as submitted. I've played around with Icon Composer a bit but haven't managed to turn this off there. And would prefer to just submit the png's. Thank you!

Something happened with my Xcode 26.4 install, I've never had this happen before. I get Xcode 26.4 installed, but the simulators aren't installed. And nothing pops up to "install required simulators". In Devices & Simulators I click the + to install a new simulator, and the beachball just spins and Xcode becomes unresponsive. I've tried quitting and restarting Xcode, reinstalling it (using both xcodes command line tool and the app store), removing Xcode and reinstalling, rebooting after removing Xcode and before reinstalling. Not sure what to try next. Feels like something is left over from uninstalling that's hanging it up. But I've no idea what. I could use some Apple Xcode team help here.

Following an unexpected error message while working in Xcode, the project file xcodeproj is no longer synced in iCloud Drive. The Finder shows a cloud icon with a ! and an error message : (NSFileProviderErrorDomain error -2005.) If the local file is zipped, and unzipped elsewhere on iCloud Drive, then the unzipped file can still not be iCloud Synced. Restoring the file from a Time Machine archive does not solve the issue. Apple Care Support finds that iCloud Drive is working fine except for this xcodeproj file and says the issue is Xcode related.