TestFlight | KSP Mod that provides a part research and reliability system

Took me a while to find this out. There were a lot of references to using iTunes, which is no longer available, and no references to using Finder, or alternatively Apple Configurator 2.

• Your device is added to your provisioning profile. This is automatically done by Xcode when you select the device and build the app onto the device.
• Plug your device in
• Archive the application (create the .xcarchive): Select the target device (e.g. arm64/ a physical iPhone 12) and archive the app: Product > Archive
• In the Organizers window, click Distribute App, and select Ad Hoc. Continue with the defaults options or customise to your liking. This should create a folder containing a .ipa file.

As Paulw11 said in the comments, you can do this in Finder. Select the device in Finder and drag the .ipa file onto the device details.

• Install Apple Configurator 2. Drag the .ipa file found in the exported directory in finder (exported from Xcode) onto the iOS screen inside the Apple Configurator 2 window, and the iOS app will be installed:

Finally, you should see this step, and the application will be available on your home screen.

Command line: As How to install an ipa/app file into iPhone with command line? states, if you have Apple Configuration 2 installed, you can open it and click "Apple Configurator 2" on Menu Bar, and install Automation tools. Then, cfgutil is available to you,

• so you can run: cfgutil install-app ipa-file.ipa

You cannot use semaphores in conjunction with async-await. See Swift concurrency: Behind the scenes:

[Primitives] like semaphores ... are unsafe to use with Swift concurrency. This is because they hide dependency information from the Swift runtime, but introduce a dependency in execution in your code. Since the runtime is unaware of this dependency, it cannot make the right scheduling decisions and resolve them. In particular, do not use primitives that create unstructured tasks and then retroactively introduce a dependency across task boundaries by using a semaphore or an unsafe primitive. Such a code pattern means that a thread can block indefinitely against the semaphore until another thread is able to unblock it. This violates the runtime contract of forward progress for threads.

You might consider testing with the LIBDISPATCH_COOPERATIVE_POOL_STRICT environment variable as discussed here, in the same video.

You ask:

I'm trying to bridge the divide between synchronous and asynchronous code (perhaps the wrong way).

You should refactor the code that calls this synchronous method to adopt asynchronous pattern, and then excise all blocking API (e.g., semaphore wait, dispatch group wait, etc.). Those were anti-patterns in the GCD world and are to be avoided within Swift concurrency. I understand why developers who are unfamiliar with asynchronous programming are so attracted to those synchronous anti-patterns, but it has always been a mistake, and should be excised from one’s code.

Bottom line, in Swift concurrency one must “maintain a runtime contract that threads are always able to make forward progress.” Just embrace asynchronous patterns (i.e., stay within async-await without any old-school thread-blocking techniques) and you should be good.

FWIW, the Swift concurrency: Update a sample app shows interesting techniques for incrementally updating an old app. E.g., mark this blocking method as deprecated, and then the compiler will warn you where it is called and you can direct your refactoring efforts to those offending routines.

I got this working. I used an older version of Xcode (12.5.1) to archive a build. New build (archived from older version of Xcode) from TestFlight is working on iOS 14+ and iOS 15+.

I think the closet thing you can do is

1) Connect your phone with a usb to your computer

2) You have to press trust device

3) Open up the file ios/__YOUR_PROJECT_NAME_.xcworkspace

4) On the top you will something like this below. Click where it says "iPhone 12 Pro Max" and choose your phone out of the options

5) Finally press the arrow to run

The name of the pod and resource bundle being the same causes issue. Try putting a unique name for the resource bundle

TestFlight ignores the sandbox accounts (which we add to Settings -> Apps-Store -> Sandbox account) and uses the main account

That is correct behavior. The sandbox account is for when you are running an Xcode build. TestFlight, on the other hand, always uses your real account, but it doesn't charge you (and the same for your beta testers).

Ok, my issue was that I was not using Linking of react-native package correctly.

Check provisioning profile to include the device so you can install it. Here is a document you can refer to https://docs.microsoft.com/en-us/xamarin/ios/watchos/deploy-test/device

You don't need to make any code changes.

Next Steps

To resolve this issue, please revise your app to complete, remove, or fully configure any partially implemented features. Please ensure your screenshots do not include any images of demo, test, or other incomplete content

To resolve above rejection, all you need to do is remove banner advertisement from your screenshots and submit for approval again.