“Account Locked”

Hello, I’m honestly trying to understand what’s going on with the Family Controls API review process. I submitted my entitlement request on March 5, and as of today (March 19), there has been zero response. I also opened a support ticket on March 16, and that hasn’t received any response either. What’s confusing is that updates to another app on the same developer account were approved within days so clearly the account is in good standing and active. At this point, it feels like there’s no visibility into what’s happening: Is the request under review? Is it waiting for additional information? Or is it just sitting in a queue indefinitely? I understand that Family Controls is a sensitive API, but a two-week silence with no status or communication makes it very difficult to plan or ship features. For those who’ve gone through this: How long did your approval actually take? Did you receive any communication during the process? Is there any reliable way to get visibility or speed this up? Right

I am in the end stages of creating my app and apple is saying I need to include Business number and GST (RT) number - I'm Canadian and not sure how this applies to developers in other countries. Just wondering if any developers from Canada can shed light on this process of getting a GST number, the CRA is saying you can create a GST account/number once your business reaches $30,000 is revenue so its seems different than what Apple is saying to do. This is my first time creating an app and I'm a solo developer.

Hello, I’m working on a security agent plugin for Mac. The plugin provides a mechanism with custom UI via SFAuthorizationPluginView and a privileged mechanism with the business logic. The plugin needs to support unlocking the device, so I changed the authorize right to invoke my agent: class evaluate-mechanisms created 731355374.33196402 mechanisms FooBar:loginUI builtin:reset-password,privileged FooBar:authenticate,privileged builtin:authenticate,privileged modified 795624943.31730103 shared tries 10000 version 1 I also changed the system.login.screensaver right to use authorize-session-owner: class rule comment The owner or any administrator can unlock the screensaver, set rule to authenticate-session-owner-or-admin to enable SecurityAgent. created 731355374.33196402 modified 795624943.32567298 rule authenticate-session-owner version 1 I also set screenUnlockMode to 2, as was suggested in this thread: macOS Sonoma Lock Screen with SFAutorizationPluginView is not hiding the macOS de

Hello, I have an internal TestFlight build for my app PewPewApp (Apple ID 6760741808). The build is processed, assigned to an internal group, and the tester invitation is accepted. The build status shows Ready to Test / Testing in App Store Connect. However, installation from TestFlight fails with: “The requested app is not available or doesn’t exist.” Could you please check whether there is an account-level or backend TestFlight distribution issue affecting this app/build? Thank you.

Help. I paid for the subscription 2 days ago (50 hours ago), the account still hasn't been activated. Support doesn't answer for 2 days either. I called, they said they couldn't help in any way. What to do??? Serial number: 2-8711222928 Order ID: MTFKZHZFFT

Hi everyone, I’m currently trying to set up a business account on the Apple Developer Console, and I’ve run into a really frustrating issue. Last month, I was asked to submit additional documents for verification. I submitted everything as requested and received a confirmation email: “Thank you for providing the documents we requested. We will review them and follow up with you within two business days.” However, weeks passed with no update. About 1–2 weeks ago, I reached out to support again. I was asked to re-submit the same documents, which I did. Once again, I received the same confirmation email stating a response would come within two business days. It’s now been 7 days since that second submission, and still no response. At this point, I’m not sure what I’m doing wrong or if this is just a delay on Apple’s side. What’s more confusing is that we’ve successfully created developer accounts on other platforms (like Google Play) using the same business information and DUNS number, with ver

Hi everyone, I’m honestly trying to understand what’s going on with the Family Controls API review process. I submitted my entitlement request on March 5, and as of today (March 19), there has been zero response. I also opened a support ticket on March 16, and that hasn’t received any response either. What’s confusing is that updates to another app on the same developer account were approved within days — so clearly the account is in good standing and active. At this point, it feels like there’s no visibility into what’s happening: Is the request under review? Is it waiting for additional information? Or is it just sitting in a queue indefinitely? I understand that Family Controls is a sensitive API, but a two-week silence with no status or communication makes it very difficult to plan or ship features. For those who’ve gone through this: How long did your approval actually take? Did you receive any communication during the process? Is there any reliable way to get visibility or speed this u

Hey everyone, I'm managing CI/CD pipelines for around 45 iOS apps across different Apple Developer accounts. One recurring pain point is blocked pipelines due to unsigned agreements. Things like the Paid Applications Agreement and the Apple Developer Program License Agreement. I built an internal dashboard to flag these before they block a release, but I'm hitting a wall with detection accuracy. Since there's no dedicated endpoint for agreement status, I'm running three probes per account and checking for 403 FORBIDDEN.REQUIRED_AGREEMENTS_MISSING_OR_EXPIRED: GET /v1/agreements GET /v1/bundleIds?filter[identifier]={bundleId}&filter[platform]=IOS GET /v1/certificates?limit=1 Case 1 : Works perfectly. Account has Apple Developer Program License Agreement has been updated and needs to be reviewed : All three endpoint return 403 (In this case, the step 1 is enough) # Step 1 /v1/agreements → HTTP 403 ⛔ BLOCKED # Step 2 /v1/bundleIds → HTTP 403 ⛔ BLOCKED # Step 3 /v1/certificates → HTT