Sorry, is that a new question, or?

Obj-C? Swift? SwiftUI? ... Show some code.

Any workarounds other than continue trying?  If you're using Safari on macOS, or Transporter, not likely. The backend is being hammered right now, which is usual, but made all the worse because Apple decided to blindside devs with such a compacted window between new tools and release to the public. Sit on your hands until 14.x hits the streets, then see how it goes. Good luck.

Outside of disabling updates globally, there is no way to avoid the MAS sniffing your applications and blacklisting individual apps. I think it's not uncommon for the store to ignore non-MAS installs, even when the build number is the same. Pick one process and stick with it.

Maybe some help in this recent similar thread? App Store Connect Rejects Binary - Unable to Compile Bitcode https://developer.apple.com/forums/thread/119012

When using 3rd party tools/SDKs, it can be more helpful to seek support from the authors of those products, vs. devForums which are Apple IDE-centric, thanks and good luck.

From the page for beta/applications the 12 GM blurb says this about that: "For development on macOS Big Sur or to support Apple silicon, continue to use Xcode 12 beta 6."

Reviews and ratings use current purchasing/download activity. I think that once that record is interrupted, you need to build it again. Perhaps if you updated that app, it's previous record would be restored, but I you'd need to contact support directly to confirm current practice. Good luck.

Without a paid Developer Program Account, you can only test via the Simulator, and to a small number of devices, connected to your mac while using Xcode. See this link for details on using Xcode's free provisioning: h ttps://steemit.com/xcode/@ktsteemit/xcode-free-provisioning

Eres uno de muchos en la misma situación. No veo una forma sencilla de solucionar su problema. See: https://developer.apple.com/forums/thread/126314

Glad you sorted it out, thanks for the followup, good luck w/your apps. Ken

Ever since installing the Xcode 12 GM Wonder if 12's sails are more trimmed when running under a release version of BigSur...

>...ended trying this application The processes outilined in the docs - https://developer.apple.com/documentation/xcode/preparing_your_app_for_distribution are the only ones you should be using: Provide a Launch Screen (iOS) A launch screen is a user interface file that appears immediately when your app launches, then is quickly replaced with your app's first screen. The launch screen simply enhances the user experience by providing something for the user to view while your app is launching. Edit the launch screen file, called LaunchScreen.storyboard, that is in the project when you create it from a template. Otherwise, you can add a launch screen file to - https://help.apple.com/xcode/mac/current/#/dev765148f31 an existing project. For information about designing a launch screen, read Launch Screen in Human Interface Guidelines. - https://developer.apple.com/design/human-interface-guidelines/ios/icons-and-images/launch-screen/

if it is a bug  I'd file one, and see what comes back, being sure to add your report numbers to your thread for ref. As well, you might consider burning a support ticket w/DTS via the Member Center, having a project that demos the issue ready to hand off. Good luck.

We now not only have a team of testers, but also have them working remotely.  If you're asking here, TestFlight is perfect, and is perhaps the only thing in your future at this point. My advice at this point is to create a small/Tiger team that commits to an all Apple IDE, training them as trainers for the larger group. we will need to complete two separate builds, one for QC and one for Production. Seperate only in the sense that the basic difference in those two would be to strip test-centric code, comments, then, how they are signed. The closer one is to the other, the better. I'd take a debug/QC build, wash it clean, then use it to generate a store signed build. Resist a dual path otherwise. Don't bother generating production/release builds until you've locked down QC builds post-test. Don't get creative...Apple provides a tightly controlled IDE that is only your friend when you adhere to it. Look into using GIT for source control. Good luck.