Visual Studio remotebuild "No 'iOS Development' signing certificate..."

I have an Ionic app which I'm trying to package to distribute for both iOS and Android. The Android process has been remarkably easy (thank you very much Ionic, MS and Google). Meanwhile, the Apple process has been nightmarishly difficult. After solving numerous problems with the build.json to provide the correct data to XCode (on a MacInCloud), I've currently hit a brick wall that's blocked me now for two days.

I've created an App Store distribution certificate on my apple developer site. I've then used that certificate to create an App Store provisioning profile, which I've downloaded so I can extract the profile's UUID. With all of that information, I've created the following build.json (with UUID's faked out but same structure):

"ios": {
  "release": {
    "developmentTeam": "1AAAA11111",
    "codeSignIdentity": "iPhone Developer",
    "packageType": "app-store",
    "provisioningProfile": "1a1f1a1-1a1a-11aa-a11a-111aa1a1a111"
   }
}

I then connect to the remote device and can watch it doing work on the MacInCloud, so everything looks good there. The command it sends which triggers the failure is:

xcodebuild with args: -xcconfig,/Users/user908471/.taco_home/remote-builds/taco-remote/builds/2538/cordovaApp/platforms/ios/cordova/build-release.xcconfig,-workspace,Cincy Christmas.xcworkspace,-scheme,Cincy Christmas,-configuration,Release,-destination,generic/platform=iOS,-archivePath,Cincy Christmas.xcarchive,archive,CONFIGURATION_BUILD_DIR=/Users/user908471/.taco_home/remote-builds/taco-remote/builds/2538/cordovaApp/platforms/ios/build/device,SHARED_PRECOMPS_DIR=/Users/user908471/.taco_home/remote-builds/taco-remote/builds/2538/cordovaApp/platforms/ios/build/sharedpch

And when it finally throws an error, this is what I get back:

Code Signing Error No signing certificate "iOS Development" found: No "iOS Development" signing certificate matching team ID "1AAAA11111" with a private key was found.

Why is it even trying to look for an iOS Development signing certificate? Do I have something set up incorrectly which will pick up the distribution profile/certificate I verified matches what's in the build.json.

Any ideas?