-
-
Notifications
You must be signed in to change notification settings - Fork 197
Export fails when using provisioning in build.xconfig and XCode9.1 #3222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@dtopuzov @PeterStaev : I am getting same error..!! NativeScript/NativeScript#5059 |
@PeterStaev , @dtopuzov : does this issue is resolved ? |
Any update on this issue? I keep getting this on a freshly installed MacBookPro with Xcode 9.2 and tns 3.4. EDIT: Sorry, issue with manual provisioning profiles. Switched to Automatic, and it worked. |
I'm having the same error when specifying the provisioning profile in the .xcconfig file. When removing the PROVISIONING_PROFILE option from the .xcconfig file and supplying it through the cli with the --provision parameter the build succeeds and exports an .ipa file. XCode: 9.2 |
same here. And @jvdonk solution does not even work for me. It feels as if this error is popping up ever so often. Specifically, when not using automatic code signing but manual signing style. It's not yet clear to me when to set up things in .xcconfig and when not. Right now, I cannot use any of the tns commands to run a build on an iOS device. Only option for now is to open the xcode propject in Xcode directly and run it there... which is kind of annoying as livesync etc. does not work. Also, I'm not sure if the exportOptions plist file that gets created when excodebuild exports the archive as an deployable IPA is correct. tns-ios: 3.4.1 |
Did this ever get resolved or root caused? It's been a few years, but I'm running in to the same In the meantime, the work around the solves the problem for me is to explicitly pass my provisioning profile UUID on the command line: |
|
I was having this problem. The temp fix @lord-zeus provided worked, however, will this issue be resolved? |
This is the same problem as #3046 but when using the
build.xconfig
file to supply provisioning instead of the CLI options. I'm using CLI 3.3 and have the following setup in thebuild.xconfig
The received error is:
The text was updated successfully, but these errors were encountered: