Xcode 12 is not yet mandated, more like April 2021 - see: https://developer.apple.com/news/ ...keeping in mind that there subtle differenences between what can be used when building, vs. what is used for submitting/uploading, and, if you are targeting iOS or macOS. I'm not aware of an 'official'comprehensive summary, but you should see: https://developer.apple.com/news/releases/ https://developer.apple.com/support/app-store-improvements/ https://developer.apple.com/app-store/review/guidelines/#introduction https://developer.apple.com/news/?id=03262020b

Yes. If you want to test/support iOS 14.x specifically, you need to build against it, specifically with a compatible Xcode (12.x), then push that build out to testers with iOS 14.x compatible devices.

Depends...not just in one place, if that's what you're asking. A script that walks likely suspect locales is required to sniff them out. Otherwise, it is the dev's responsibility to copy from/to, at time of, but... don't take the error literally, as it could come from having dupes, etc. making the task a delete/ignore, instead. Just for grins, try this work-around: in the Xcode -> Organizer window, after you create an archive, right-click on your new archive press "Show in Finder" right click on the archive in Finder press "Show Package Contents" delete the 'SwiftSupport' folder ...and then go again. Good luck.

...on the release version of Xcode 12 (12A7209) Might want to note this from the Xcode 12 GM (12A7209) download blurb... "For development on macOS Big Sur or to support Apple silicon, continue to use Xcode 12 beta 6."

How we can do that without uploading and submitting a new version? You can't do that. Updating an app to a new version is the only method that allows app name change in the store. we would like to use Triviador Russia as the localized name of the app. You can do that, in fact, it is allowed and quite common to use unique names when localising an app. Good luck.

As devForums aren't formal enhancement requests, feel free to file one via the feedback/bug report link below, being sure to add your report # to your thread for reference, thanks and good luck.

Quoting the Apple Developer Agreement: - https://developer.apple.com/terms/apple-developer-agreement/Apple-Developer-Agreement-English.pdf 1. Relationship With Apple; Apple ID and Password. You understand and agree that by registering with Apple to become an Apple Developer (“Apple Developer”), no legal partnership or agency relationship is created between you and Apple. You agree not to represent otherwise. You also certify that you are at least thirteen years of age and you represent that you are legally permitted to register as an Apple Developer. This Agreement is void where prohibited by law and the right to register as an Apple Developer is not granted in such jurisdictions. Unless otherwise agreed or permitted by Apple in writing, you cannot share or transfer any benefits you receive from Apple in connection with being an Apple Developer. The Apple ID and password you use to log into your Apple Developer account cannot be shared in any way or with anyone. You are responsible for maintaining the confidentiality of your Apple ID and password and for any activity in connection with your account. The part about 'legally permitted' means you are of legal age to enter into a contract as defined by your country. 18, as an example, is the legal age for California, USA, where Apple is headquartered - earlier agreements used to use that number, where the legalese has been made more global since, in order to accomodate legal age requirements that can differ from locale to locale. Some younger devs have a parent/legal guadian buy the dev account, and then when they are of legal age, they buy their own account and transfer their apps over to it. Keep in mind that the account owner assumes all legal responsibiity, including any tax burden that results from store revenue. Good luck.

Confirm to use Safari on macOS. Payment otherwise is no different than your average Apple Store purchase. Go there, create an account to make purchases, edit payment options and proceed. Good luck.

Are there any paid 3rd parties who can accommodate the App publishing service on our behalf? Apple expects to deal with principles only in that example. Any other use of an owned program is unauthorizied.

You don't take a .app out of a signed archive and expect to be able to submit it, regardless if you use Transporter or not. The whole purpose of an archive in your example is to create something that is properly configured/packaged/signed for submittal to the store. If it isn't, you can submit/upload it. If for some reason you don't want to archive using Xcode, google the process to create an archive via the command line. But if your ducks are in alignment to be able to do that, Xcode should work as well, so... Your issue's root cause is being space constrained. To fix that, you'll either need to free up sufficient space and keep it there, or buy a much larger drive. As for running Xcode from an external drive - Xcode should be installed and run from your boot drive, /Applications folder, internal or external is ok, but again only if you're talking about the boot drive...way too many system hooks for it to tolerate any other configuration. Good luck.

Interesting feedback, thanks, but if you're trying to file bugs vs. asking questions, feel free to use the feedback/bug reporter link below, being sure to add your report #s to your thread for reference, and see what comes back - good luck.

What devices is your app coded to support?

Is this something you tested before and now suddenly see a change? Did you use the Product menu to 'clean build folder' when making those changes?

What is it about that window you wish to edit, exactly? Style, tint, size, border, contents, app's name only...?

Burning a support ticket w/DTS is for code level issues, so yes, more serious, typically. In your example, if the question is just a 'how-to', my opinion is that they wouldn't be able to help, but if you make a request and they can't participate, I'd expect them to tell you and give the ticket back as unused. The worst that can happen is they say 'no' ;) Suggest you simply ask for help on the forums in the mean time. Good luck.