EXPORT FAILED fse.node has conflicting provisioning settings

[iosdeveloper1001]

I am using a latest version of Cli i.e 4.0.1
I am not able to use tns run ios command for my project and getting below error.

error: exportArchive: fse.node has conflicting provisioning settings.

Error Domain=IDEProvisioningErrorDomain Code=8 "fse.node has conflicting provisioning settings." UserInfo={NSLocalizedDescription=fse.node has conflicting provisioning settings., NSLocalizedRecoverySuggestion=fse.node is automatically signed for distribution, but a conflicting code signing identity iPhone Developer has been manually specified.Remove the "signingCertificate" entry from your Export Options property list, or switch to manual signing by setting "signingStyle" to "Manual.}

[willzarem]

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.

[mathias-mcb]

Hey there,
I'm having the same issue. Could you solve it?

Any hint or note is highly appreciated. I'm stuck on the issue for a few days already.. 😞

[NickIliev]

@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.

[surdu]

@NickIliev Tried your solutions but I have 2 problems:

1. for some reason, the .app is not generated anymore:

Unable to apply changes on device: 5784c839f6bde322f71ed053979b3459900e92d5. Error is: ENOENT: no such file or directory, stat '/Us
ers/nicolae.surdu/work/capango-seeker/platforms/ios/build/device/capangoseeker.app'.

2. once you remove the platforms folder, you'll have to disable automatic signing again.

This happened on our project after we upgraded nativescript from 4.0 to 4.1 / 4.2

[surdu]

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)

[pajohns]

I've been battling with this issue for the last 8 hours. I managed to work around it so that I can at least run the app on my phone, but it'd be great if there were a better solution.

1. Build your app and run the tns build ios command
2. Open the yourapp>platforms>ios>yourapp.xcworkspace xcode workspace in xcode.
3. Choose your project on the left
4. Go to the "Signing" section in the project settings and check to ensure that "Automatically manage signing" is checked and that the team is selected.
5. Run the app on your connected iPhone.

It's not a fix rather a workaround and if anyone can shed any light on this issue, I'd be very appreciative!

[surdu]

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

[iosdeveloper1001]

I have one solution for this kind of issue, that is to search for the file ios-project-service.js at /usr/local/lib/node_modules/nativescript/lib/services this path.and search for the method name exportDevelopmentArchive and in this plistTemplate add a compileBitcode key to false

Now execute your code with provisioning profile id i.e
tns run ios --provision provision-id.

[hettiger]

@NickIliev

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.

Is the team working on a solution that does not require manual repetitive steps? I don't want to keep touching generated code.

This issue should be labeled as a bug in my opinion.

[surdu]

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.

[hettiger]

@surdu I've thought about that too but instead I tried to diff my project to a new clean 4.2 project. I couldn't find anything that would make a lot of sense to me causing this issue. We're using Sass, Webpack Builds, Firebase and whatnot. This will be a pain ... :-/

[surdu]

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

[hettiger]

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

Your app name and id remained the same when you did copy over to a new project?

Maybe it's some Xcode cache ...?

[surdu]

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.