Account Locked

Delete the associated certificates & keys from your local machine - Mac To get started use Command-Key / Spacebar (opens search) type keychain. it will bring up keychain access app in list click keychain access app Select the 2nd option [Open Keychain Access] You'll have to supply a password or whatever to get in Look under Certificates tab You'll find a developer certificate for the account. Be very careful you don't delete the wrong one You should be able to delete the associated developer certificates and it will remove the developer account -- the certificate that XCode uses to sign the apps with. You can probably determine which one is which by the associated email address. ie There is one email address tied to each developer account. Good luck

hello dear i cant upload my app on Test-flight (apple devleoper account enrolled ) fees of enrollment is paid

Thanks for that clarification. You should contact the Developer Program support team for assistance with account-related issues such as this. — Ed Ford,  DTS Engineer

hi, tks for help, When accessing my administrator user account where I can create users to have access to upload applications within the platform, when registering a new user, an error appears. I have several application developer users, but when adding a new one, an error occurs. The error in the image, I've already changed browsers, changed phones, and the same error persists. right after entering the code to verify the account.

I had the same issue and resolved it as follows: Login to your account. Click on Support in the menu Scroll down and find Contact us by phone or email Click on the button Get Started Click on Membership and Account Click on Program Enrolment Click on Phone (if this option is greyed out or not-clickable, then you are outside the opening hours of the support desk. Allow for a time difference, for example the EU support desk is in Ireland which may be a different timezone for you) Leave your number I was called back within a minute. First you get a tape and you have to confirm something by pressing 1, but after a minute or so, I got a chap on the phone and he solved it. Problem was, according to him, that you can not use like company details when personal details are asked. He cleared that, instructed me to wait for a couple of minutes, and when I tried again, I could proceed with the process and finally got to finish it. Good luck!

I seems to me that Apple has closed the Xcode Cloud functionality for russian accounts. Almost all recent problems with Xcode cloud on this forum are from russian developers. It's very sad, actually.

Hi @DTS Engineer, Our new metrics indicate that the one-way issue caused by audio session not activated accounts for more than 50% of cases. Given this significant percentage, could you please revisit and reexamine this issue? Thank you

I submitted my app for review more than 3 days ago, but it still hasn’t been approved. Normally, my versions get reviewed within 24 hours. Recently, I’m not sure if the delay is due to my account nearing expiration, but I have already extended my developer membership for another year.

[quote='851379022, Darrilla, /thread/791996?answerId=851379022#851379022, /profile/Darrilla'] the creating a new application DOES NOT create an Info.plist. [/quote] Right. Xcode changed the way it handles Info.plist files, only creating one in your project if the app using non-standard keys. [quote='851379022, Darrilla, /thread/791996?answerId=851379022#851379022, /profile/Darrilla'] Telling someone to delete a key that shows up in that file [/quote] I reviewed the latest Signing a daemon with a restricted entitlement and I don’t see where it says that. It does say: Switch to the Info tab and delete all the app-specific items but that’s not referring to the Info.plist file directly but rather the Info tab of the target editor. Having said that, there is one gnarly problem with the Signing a daemon with a restricted entitlement instructions, namely that it dosen’t recommend clearing the Enable Debug Dylib Support build setting. With that setting enabled you end up with a structure like this: quinn@Mac Debug %