nativescript-cli: EXPORT FAILED fse.node has conflicting provisioning settings

Ok, managed to find a scenario how to reproduce this issue:

1. install nativescript 4.0: npm install nativescript@4.0
2. create a new project: tns create TestProj
3. install nativescript 4.2: npm install nativescript@4.2
4. try to run the above created project on an iOS device (not simulator): cd TestProj; tns run ios

The problem appears to be when trying to run projects created with a previous version of tns. Running projects created with v4.2 work as expected.

Versions: MacOS: v10.12.6 (16G1510) XCode: v9.2 (9C40b)

@mathias-mcb try the solution suggested in the error log

or switch to manual signing by setting "signingStyle" to "Manual.}

Basically, do this - open the built project in XCode and set the signing to manual.

You must pay attention to the package.json and their dependencies, if you have some plugin that use some package like chockidar that behinds use fsevents package (for example nativescript-dev-sass) and that plugin is listed in the dependencies instead of the devDependencies section then the fse.node error throws up, simple move that plugin package from dependencies to devDependencies and then run:

rm -rf node_modules
tns platform remove ios

Now you can generate an IPA or run over an emulator using the CLI.

Somehow "@angular/cli": "^6.0.8", Came back in my dependencies, where it should be in devDependencies (upgrading to the latest @next). Moved to devDependencies, removed node_modules abomination and did npm install

Alright… I’ve removed the fsevent package. I’m not sure why it’s in my node_modules, and therefore in my tns_modules.

Yes, they remained the same. In the example I gave above I didn’t build the project, just created it, so I don’t think it’s the cache.

@hettiger I also made the diff in between a new and an old clean project and arrived to the same conclusion as you.

In order to solve the problem we had to create a blank new project using the latest NativeScript and copy all files to the new app. That was unpleasant and definitely not the proper solution, but it worked.

@pajohns This doesn’t solve the problem in my case 😞

Same error here:

018-05-22 12:08:34.361 xcodebuild[30599:2756740] [MT] IDEDistribution: Step failed: <IDEDistributionSigningAssetsStep: 0x7ff39660aea0>: Error Domain=IDEDistri
butionSigningAssetStepErrorDomain Code=0 "Locating signing assets failed." UserInfo={NSLocalizedDescription=Locating signing assets failed., IDEDistributionSig
ningAssetStepUnderlyingErrors=(
    "Error Domain=IDEProvisioningErrorDomain Code=8 \"ios-device-lib has conflicting provisioning settings.\" UserInfo={NSLocalizedDescription=ios-device-lib h
as conflicting provisioning settings., NSLocalizedRecoverySuggestion=ios-device-lib is automatically signed for distribution, but a conflicting code signing id
entity iPhone Distribution has been manually specified. Remove the \"signingCertificate\" entry from your Export Options property list, or switch to manual sig
ning by setting \"signingStyle\" to \"Manual.}",
    "Error Domain=IDEProvisioningErrorDomain Code=8 \"fse.node has conflicting provisioning settings.\" UserInfo={NSLocalizedDescription=fse.node has conflicti
ng provisioning settings., NSLocalizedRecoverySuggestion=fse.node is automatically signed for distribution, but a conflicting code signing identity iPhone Dist
ribution has been manually specified. Remove the \"signingCertificate\" entry from your Export Options property list, or switch to manual signing by setting \"
signingStyle\" to \"Manual.}",
    "Error Domain=IDEProvisioningErrorDomain Code=8 \"adb has conflicting provisioning settings.\" UserInfo={NSLocalizedDescription=adb has conflicting provisi
oning settings., NSLocalizedRecoverySuggestion=adb is automatically signed for distribution, but a conflicting code signing identity iPhone Distribution has be
en manually specified. Remove the \"signingCertificate\" entry from your Export Options property list, or switch to manual signing by setting \"signingStyle\"
to \"Manual.}",
    "Error Domain=IDEProvisioningErrorDomain Code=8 \"fsevents.o has conflicting provisioning settings.\" UserInfo={NSLocalizedDescription=fsevents.o has confl
icting provisioning settings., NSLocalizedRecoverySuggestion=fsevents.o is automatically signed for distribution, but a conflicting code signing identity iPhon
e Distribution has been manually specified. Remove the \"signingCertificate\" entry from your Export Options property list, or switch to manual signing by sett
ing \"signingStyle\" to \"Manual.}",
    "Error Domain=IDEProvisioningErrorDomain Code=8 \"fse.node has conflicting provisioning settings.\" UserInfo={NSLocalizedDescription=fse.node has conflicti
ng provisioning settings., NSLocalizedRecoverySuggestion=fse.node is automatically signed for distribution, but a conflicting code signing identity iPhone Dist
ribution has been manually specified. Remove the \"signingCertificate\" entry from your Export Options property list, or switch to manual signing by setting \"
signingStyle\" to \"Manual.}",
    "Error Domain=IDEProvisioningErrorDomain Code=8 \"fse.node has conflicting provisioning settings.\" UserInfo={NSLocalizedDescription=fse.node has conflicti
ng provisioning settings., NSLocalizedRecoverySuggestion=fse.node is automatically signed for distribution, but a conflicting code signing identity iPhone Dist
ribution has been manually specified. Remove the \"signingCertificate\" entry from your Export Options property list, or switch to manual signing by setting \"
signingStyle\" to \"Manual.}",
    "Error Domain=IDEProvisioningErrorDomain Code=8 \"fse.node has conflicting provisioning settings.\" UserInfo={NSLocalizedDescription=fse.node has conflicti
ng provisioning settings., NSLocalizedRecoverySuggestion=fse.node is automatically signed for distribution, but a conflicting code signing identity iPhone Dist
ribution has been manually specified. Remove the \"signingCertificate\" entry from your Export Options property list, or switch to manual signing by setting \"
signingStyle\" to \"Manual.}",
    "Error Domain=IDEProvisioningErrorDomain Code=8 \"fse.node has conflicting provisioning settings.\" UserInfo={NSLocalizedDescription=fse.node has conflicti
ng provisioning settings., NSLocalizedRecoverySuggestion=fse.node is automatically signed for distribution, but a conflicting code signing identity iPhone Dist
ribution has been manually specified. Remove the \"signingCertificate\" entry from your Export Options property list, or switch to manual signing by setting \"
signingStyle\" to \"Manual.}",
    "Error Domain=IDEProvisioningErrorDomain Code=8 \"fse.node has conflicting provisioning settings.\" UserInfo={NSLocalizedDescription=fse.node has conflicti
ng provisioning settings., NSLocalizedRecoverySuggestion=fse.node is automatically signed for distribution, but a conflicting code signing identity iPhone Dist
ribution has been manually specified. Remove the \"signingCertificate\" entry from your Export Options property list, or switch to manual signing by setting \"
signingStyle\" to \"Manual.}",
    "Error Domain=IDEProvisioningErrorDomain Code=8 \"fse.node has conflicting provisioning settings.\" UserInfo={NSLocalizedDescription=fse.node has conflicti
ng provisioning settings., NSLocalizedRecoverySuggestion=fse.node is automatically signed for distribution, but a conflicting code signing identity iPhone Dist
ribution has been manually specified. Remove the \"signingCertificate\" entry from your Export Options property list, or switch to manual signing by setting \"
signingStyle\" to \"Manual.}",
    "Error Domain=IDEProvisioningErrorDomain Code=8 \".node has conflicting provisioning settings.\" UserInfo={NSLocalizedDescription=.node has conflicting pro
visioning settings., NSLocalizedRecoverySuggestion=.node is automatically signed for distribution, but a conflicting code signing identity iPhone Distribution
has been manually specified. Remove the \"signingCertificate\" entry from your Export Options property list, or switch to manual signing by setting \"signingSt
yle\" to \"Manual.}"

Tns doctor:

✔ Getting environment information

✔ Your ANDROID_HOME environment variable is set and points to correct directory.
✔ Your adb from the Android SDK is correctly installed.
✔ The Android SDK is installed.
✔ A compatible Android SDK for compilation is found.
✔ Javac is installed and is configured properly.
✔ The Java Development Kit (JDK) is installed and is configured properly.
✔ Xcode is installed and is configured properly.
✔ xcodeproj is installed and is configured properly.
✔ CocoaPods are installed.
✔ CocoaPods update is not required.
✔ CocoaPods are configured properly.
✔ Your current CocoaPods version is newer than 1.0.0.
✔ Python installed and configured correctly.
✔ The Python 'six' package is found.
No issues were detected.
✔ Getting NativeScript components versions information...
⚠ Update available for component nativescript. Your current version is 4.0.1 and the latest available version is 4.0.2.
⚠ Update available for component tns-core-modules. Your current version is 4.0.0 and the latest available version is 4.0.1.
⚠ Update available for component tns-android. Your current version is 4.0.0 and the latest available version is 4.0.1.
✔ Component tns-ios has 4.0.1 version and is up to date.