Nativescript-cli: Auto provision certificate signing while running on real device does not work
Please, provide the details below:
Did you verify this is a real problem by searching the NativeScript Forum and the other open issues in this repo?
Yes
Tell us about the problem
While deploying to a real iOS device running tns run ios causes an error while signing. Passing the 'Provision Name' resolves this issue and the app is deployed on the device correctly.
Which platform(s) does your issue occur on?
iOS
Please provide the following version numbers that your issue occurs with:
- CLI:
4.2.0-2018-07-10-11964 - Cross-platform modules:
^4.1.0 - Runtime(s):
4.1.0
Please tell us how to recreate the issue in as much detail as possible.
Download this app and do tns run ios while an real iOS device is connected to your Mac
VladimirAmiorkov
All 2 comments
Hi @VladimirAmiorkov,
Running tns run ios on a real device is using the automatically manage signing feature of xcode and it seems that you are getting an error during this automatic signing.
I see that you are trying to run one of our demo apps and the most common error there is:
Code Signing Error: Failed to create provisioning profile. The app ID "org.nativescript.demo" cannot be registered to your development team. Change your bundle identifier toa unique string to try again.
Code Signing Error: No profiles for 'org.nativescript.demo' were found: Xcode couldn't find any iOS App Development provisioning profiles matching 'org.nativescript.demo'.
Most of the ids of the plugin demo apps are locked. The above-mentioned error is thrown if you are using a free or enterprise Apple developer account where it seems that the automatic signing cannot use wildcard profiles. It also cannot automatically create a new one because the app id is already locked.
In order to run the plugin demo apps on a real device, you need to specify your wildcard profile using the tns run ios --provision YourProvisionProfileNameHere (you could list the available provisions using tns run ios --provision). You could also change the app id of the demo app to something unique and use tns run ios with the xcode automatic singning feature.
DimitarTachev
on 17 Jul 2018
Thank you @DimitarTachev . Indeed this is the case, I will close this issue.
VladimirAmiorkov
on 19 Jul 2018
Related issues
NickIliev
路
3Comments
Anilinfo2015
路
3Comments
StevenSeo
路
3Comments
bradmartin
路
3Comments
donker
路
3Comments
Most helpful comment
Hi @VladimirAmiorkov,
Running
tns run ioson a real device is using theautomatically manage signingfeature ofxcodeand it seems that you are getting an error during this automatic signing.I see that you are trying to run one of our
demo appsand the most common error there is:Most of the ids of the plugin demo apps are locked. The above-mentioned error is thrown if you are using a free or enterprise Apple developer account where it seems that the automatic signing cannot use wildcard profiles. It also cannot automatically create a new one because the app id is already locked.
In order to run the plugin demo apps on a real device, you need to specify your wildcard profile using the
tns run ios --provision YourProvisionProfileNameHere(you could list the available provisions usingtns run ios --provision). You could also change the app id of the demo app to something unique and usetns run ioswith the xcode automatic singning feature.