Open PeterStaev opened 7 years ago
Edit: @PeterStaev Confirmed this is what is causing a lot of headache right now, it's trying to select my development certificate when archiving. How do we work around this until a patch is released?
Am not sure if this is related to 3.x, XCode, or something else -- it's happening for someone on ionic too: https://forum.ionicframework.com/t/ionic-prod-release-build-incorrectly-adding-development-provision-profile/98940
Was a workaround ever found?
I've spent hours debugging a problem with an IPA and ends ups that the CLI does not respect the
--release
flag when it does archiving. I have the following in mybuild.xconfig
:When I run
tns build ios --for-device --release
and I inspect the contents of theplatforms/ios/build/device/<myapp>.app
theembedded.mobileprovision
is the correct one (theRelease
one above). But if I extract the IPA file's Payload and inspect theembeeded.mobileprovision
there it is the wrong one (theDebug
one above). If I go toplatforms/ios/archive
and open the archive in XCode and export for AdHoc (for example) the correct provisioning profile is being used.Expected behavior The CLI should use the same provision profile when archiving as the one used to build the
.app
file.