An app name is attached to your account when adding a new app to App Store Connect. That name is then unavailable to other devs. It's yours. Just be sure to use the name with an app for the store in due course. If it just sits without use, it will eventually time out and be returned to the pool.

How many teams are you on, with how many different Apple IDs? What is your Member Center role vs. App Store Connect role? Confirm you are using the Apple ID to login that you think you should, sign out from all services with any other Apple IDs, and confirm your roles in both examples are of sufficient authority to perform the actions you are attempting. If you are using your own Developer Program account and are not on any other teams, etc. be sure to use Safari on macOS to interact with the backend and be patient, trying again later. If this is a brand new account, same advice. Good luck.

The typical wait time when you are outside the US is 2 weeks or longer. Be patient and good luck.

Just tap agree/accept. Can't help w/VO except the obvious suggestion to disable it, at least temporarily, if it's getting in the way. Alternatively, give mobile Safari on iOS a shot. Good luck.

Using Safari on macOS? Less than 28 days left? Otherwise, it seems to be a pain for many... See this ongoing thread: https://developer.apple.com/forums/thread/126314 Good luck.

Validate your IBAN here: https://ww w.iban.com/iban-checker And when using it, confirm there is not a leading or trailing space. Still no joy, keep in mind that many people have been complaining about not being able to purchase accounts... Good luck.

There is no mandate for you to update, only your desire towards new features that iOS 14 may provide specific to your app, and of course any issues that may be new to it when running under iOS 14. Best to test against it to your users don't have to ;), in which case you'll need Xcode 12. Apple usually does a good job of not breaking current apps in the store when a major new iOS hits the street, but again, get your testing done so you can proceed accordingly. Good luck.

Sweepstakes is sweepstakes, lotteries is lotteries... _Quoting the current ASRGs:_ - https://developer.apple.com/app-store/review/guidelines/#introduction ..5.3 Gaming, Gambling, and Lotteries Gambling, gaming, and lotteries can be tricky to manage and tend to be one of the most regulated offerings on the App Store. Only include this functionality if you’ve fully vetted your legal obligations everywhere you make your app available and are prepared for extra time during the review process. Some things to keep in mind: -- ..5.3.1 Sweepstakes and contests must be sponsored by the developer of the app. -- ..5.3.2 Official rules for sweepstakes, contests, and raffles must be presented in the app and make clear that Apple is not a sponsor or involved in the activity in any manner.- ..5.3.3 Apps may not use in-app purchase to purchase credit or currency for use in conjunction with real money gaming of any kind, and may not enable people to purchase lottery or raffle tickets or initiate fund transfers in the app. - ..5.3.4 Apps that offer real money gaming (e.g. sports betting, poker, casino games, horse racing) or lotteries must have necessary licensing and permissions in the locations where the App is used, must be geo-restricted to those locations, and must be free on the App Store. Illegal gambling aids, including card counters, are not permitted on the App Store. Lottery apps must have consideration, chance, and a prize. Will Apple allow me to do this or will my app get rejected?  App Review isn't here, there are no pre-reviews, no one here can promise what App Review will/won't allow/reject. You'll only be afforded the opinions of unpaid referrees here, and mine is that based on the brief app exposition provided, with no details on if the app is paid, free, IAP, or how rewards are earned and then redeemed/converted to sweepstakes entries, odds of winning, etc. etc. you may have to build it, submit it and run the review gauntlet, fingers crossed. Good luck.

The current version requires OS X 12.0 Any idea why users would see such a comment? My guess is that there are several compatibility flags on the backend that are being reset right now. Factor in cached info on multiple servers in various locations, and the scene is set. Current concerns noted, but it might be Friday before things quite down across the board, at the soonest.

When using Xcode's free provisioning, the ability to interact with the backend is limited, including the ability to see active bundleIDs. The paid dev account is not associated with anything you did when using Xcode's free provisioning. Any bundleIDs created with free provisioning are tied to the AppleID used at that time. Side note I hope you didn't use the same Apple ID tied to free provisioning with your new paid dev program account..those should be separate and unique. Suggest you do as the error recommends and simply create a new, unique bundleID - keep in mind they are free and you can create as many as you like. It is only important that they are in the proper format and unique with each app you create. Write this off as a learning experience, move on and be happy. If you care to go to the trouble, you might try asking support directly if there is anything they can do via the 'contact us' link below, but I would keep expectations low, and not be surprised if they say oh well and send you back here to devForums. Good luck.

32 GB ram. 2.9 GHz 6-Core Intel Core i9. Good info, thanks. As a data point, running Xcode 12 GM on a soon-to-be-obsoleted late 2012 mac mini w/16 GB ram, it consumed shockingly little CPU, single digits, and less than 300mb ram when handling a simple hello world project to an iPhone 8. I then built a legacy mid-sized project, and while the machine load remained low, it took it's time walking thru/indexing 125 tasks, finally completing with no other drama. The mini remained responsive as well. Definetly a contrast over previous versions. Quite the surprise, actually. Doesn't help you of course, but hopefully whatever is going on comes down to bugs that can be squashed soon. Good luck.

Xcode 11 won't know what to do with that device now. Either grab Xcode 12 GM download, or wait a bit longer for the public version of Xcode 12 from the Mac App Store. Not sure I'd bother with Xcode 12 b6, unless I still wanted to be able to dev for Big Sur right now. Good luck.

Quoting the Xcode 12 GM download blurb: "For development on macOS Big Sur or to support Apple silicon, continue to use Xcode 12 beta 6."

"is crashing" is not enuf information to help you. If there's a crash, there is a detailed crash report, the purpose of which is to enable specific troubleshooting. Apple docs will teach you how to deal with one.

I understand being stuck, and confusion in the process, but it's best to not push another binary unless specificallt told to do so, you risk going to the back of the line, at the least. I think in the case of a fullfilled request to modify meta-data, the reviewer will be notified on the backend, and take action. Good luck in any case.