I have;
- one Developement-Certificate;
- used to sign a Debug profile for my device;
- one Distribution Certificate;
- used to sign an AdHoc-profile for my device;
- used to create an App Store distribution profile;
Debug and AdHoc builds work as expected. Since I could never get the App Store distribution profile to work, I just built the app on my device with the AdHoc profile but selected Release in the configuration manager. Thus an ipa-file was created at the root of the Release directory which I could upload through the Transporter on Mac and it was accepted by TestFlight. Things changed with the Visual Studio 17.3.3 release (this was the only changing variable in my environment). The app will be treated as an AdHoc build regardless of configuration (which is probably intentional). But now I am lost completely incapable of building for TestFlight. I create the App store profiles by selecting App Store -> selecting the correct App ID -> selecting distribution cert -> selecting a name in Apple Developer. I tried this repeatedly I end up with the infamous MT1006 error every time, regardless of selecting Release or App Store in the configuration manager. Microsoft's documentation is not helpful at all in this regard as the steps described in the documentation are not even reproducible:
Click the + button, select iOS App Development and App Store, and click Continue.
I can't select both of these, it's either iOS App Developement or App Store (I'm choosing the later).
Select a signing certificate and click Continue. Select devices to include in this profile and click Continue.
I can't even select a device when selecting App Store distribution.
What am I doing wrong? I can see the issue being the fact that I cannot build my App Store release build on a device I never provisioned for, but how else am I supposed to build the archive if I can't even select a target device for the profile?