“Account Locked”

A free or reduced-cost entitlement path for non-commercial volunteer-maintained drivers If you haven't already, please file a bug asking for the dev-only entitlements to be enabled on free developer accounts, and post the bug number back here. I can't promise it will happen, but it's an interesting idea that I don't think we've really considered. Published approval criteria and timelines so projects can plan accordingly Unfortunately, publishing truly formal criteria is much more difficult than it sounds since, in practice, it's very difficult to come up with a criteria set that EXACTLY covers every reasonable use case while also excluding every possible unreasonable use case... and that assumes we could even come up with every use case. However, on this point: Even if the developer is a professional company, some legacy hardware will go unsupported because of a lack of support from the vendor. Providing a way for users who need access to older hardware would be needed. We understand that the nature

It took me a little bit to realize that tapping on the text in the Share to Files interface provided a way to change the file name - when I share one item. In some online tutorials there was a way to set the full filename (like Export.csv) - but maybe that's only when writing to the app's file directory. Would you agree? I can't really think of a clean way to be able to name 2 files in that interface - so I fully understand why that's not available - and therefore I don't plan to proceed to a feedback for this. I should be able to combine elements so that I'm only sharing 1 item in for my original request. Could you clarify how DTS works now relative to these questions answered here on the forum? Since I did ask for a DTS - does this count as one? It doesn't matter to me right now because my dev account will renew soon. Thanks so much!

Update: We received an App Review rejection on 2026-03-17 06:02 UTC for Guideline 4.1(a) (Copycats - references to OpenClaw). The notarization queue started failing at 2026-03-17 09:06 UTC, exactly 3 hours after the rejection. Could this App Review rejection have triggered a backend review of our account affecting notarization?

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 can request that we migrate you from the old process to the new process. I recomm

Did any of you got replied or a status change on the account? I am having the same issue. Bought the apple developer program 10 days ago, money went out of the bank and got the invoice in the email. I sent several suport emails and I am 10 days without a reply. I dont know what else to do.

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

Update: Two separate teams affected, detailed timeline below Team 1 (DocuAgile): 03-11 to 03-17 03:30 UTC: All Accepted (100+ successful submissions) 03-17 09:06 UTC: Suddenly all Rejected (statusCode 7000, Team is not yet configured for notarization) 03-17 12:32 UTC: Brief recovery, 2 Accepted 03-17 13:08 UTC: Back to Rejected 03-18 13:51 UTC: Recovery again, 2 Accepted 03-19 02:30 UTC onwards: All stuck In Progress, logs return not yet available Tested with a 7KB minimal test.zip — also stuck: 015ade60-c2f8-4af7-b535-3ae7fd5c9ffd Team 2 (separate account): 03-11 to 03-17 03:30 UTC: All Accepted (100+ successful submissions) 03-17 09:06 UTC: All stuck In Progress, never recovered Agreement was not signed — signed it today, still no recovery All submission logs return not yet available Earliest stuck submission: 789d40c4-ff83-469f-9b9b-2ac93183125e (2026-03-17 09:06 UTC) Latest stuck submission: ef7f8dbb-a7db-44c8-910c-532761b2a528 (2026-03-19 11:53 UTC) Both teams have valid Developer ID Application

Update: I tested with a minimal 7KB test.zip (simple signed app) using the same keychain profile. It also stuck in In Progress immediately, confirming the issue is account/team level, not related to the package content. Submission ID for test: 015ade60-c2f8-4af7-b535-3ae7fd5c9ffd

Thank you for reporting this — it's a clear and well-documented write-up. I was able to reproduce this on a MacBook M5 Max running macOS 26.3.1 (25D2128). I built a small test app that exercises both CGSetDisplayTransferByTable and CGSetDisplayTransferByFormula with several different gamma tables (identity, warm tint, inverted, red-only, gamma 1.8). On the M5 Max: Both APIs return kCGErrorSuccess Reading back the table with CGGetDisplayTransferByTable returns the correct values that were just set No visual change occurs on the display The same test app works correctly on an M5 (non-Max) machine running the same macOS build — all gamma changes are immediately visible on screen. This suggests the gamma tables are being stored correctly at the CoreGraphics level, but are not being applied to the display pipeline on M5 Max hardware. Tested on both built-in and external displays. I've related your two bugs (FB22273730 and FB22273782) together and attached the sample project I used to reproduce the problem to your

By contrast, I can sign in to the Sandbox Apple Account without issue on a physical device. The problem occurs only via Simulator. That is the expected behavior. To test in the sandbox environment, you need a physical device. For more information, see Testing In-App Purchases with sandbox. StoreKit Testing in Xcode is a local test environment for testing in-app purchases without requiring a connection to App Store servers. You can use it to test In-App Purchases in the Simulator without a Sandbox account.