EXPORT FAILED fse.node has conflicting provisioning settings #3568

iosdeveloper1001 · 2018-05-08T12:25:47Z

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

The text was updated successfully, but these errors were encountered:

willzarem · 2018-05-22T18:13:03Z

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 · 2018-06-28T09:58:47Z

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 · 2018-08-07T10:17:17Z

@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 · 2018-08-14T10:50:58Z

@NickIliev Tried your solutions but I have 2 problems:

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

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 · 2018-08-14T13:19:58Z

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

install nativescript 4.0: npm install [email protected]
create a new project: tns create TestProj
install nativescript 4.2: npm install [email protected]
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 · 2018-08-28T16:01:21Z

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.

Build your app and run the tns build ios command
Open the yourapp>platforms>ios>yourapp.xcworkspace xcode workspace in xcode.
Choose your project on the left
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.
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 · 2018-08-29T07:27:27Z

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

iosdeveloper1001 · 2018-08-30T06:02:12Z

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 · 2018-10-02T07:47:29Z

@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 · 2018-10-02T07:52:08Z

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 · 2018-10-02T07:55:42Z

@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 · 2018-10-02T08:02:13Z

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

hettiger · 2018-10-02T08:05:02Z

@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 · 2018-10-02T08:08:13Z

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 · 2018-10-02T14:41:29Z

Some further attempts of me:

npm i -g nativescript@latest
Adding DEVELOPMENT_TEAM and CODE_SIGN_IDENTITY to app/App_Resources/iOS/build.xcconfig
rm -rf node_modules && rm -rf platforms
Delete directories that are related to my app in ~/Library/Developer/Xcode/DerivedData
rm -rf ~/Library/MobileDevice/Provisioning\ Profiles
Open up the Xcode project and deactivate + activate automatic code signing

Whatever I do:

I'm not able to build for iOS using the CLI
Building with Xcode works (but it's not a solution since i need the CLI for an effective workflow...)

hettiger · 2018-10-04T10:20:16Z

I finally gave up and recreated the entire project.
Fortunately it paid off and I can continue doing actual work.

I ran tns create and then copied over my .git directory.
This greatly simplified the process in my opinion.
(I just hat to revert and diff for a while ...)

jrz · 2018-10-17T14:04:16Z

No code change, ran tns run ios again, and all now I get this thing too.

jrz · 2018-10-17T20:31:40Z

Building with xcode works until you try to sign / upload.
After f'in arround with provisioning profiles etc, it turns out fse.node is an executable that is not allowed in the package....

jrz · 2018-10-17T20:31:58Z

That also explains why it expects to be signed as Mac Developer

jrz · 2018-10-17T21:37:57Z

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

larssn · 2018-10-23T07:43:54Z

@jrz
It's used by the following modules:

├─┬ @angular/[email protected]
│ └─┬ @angular-devkit/[email protected]
│   └─┬ [email protected]
│     └── [email protected]  deduped
├─┬ @angular/[email protected]
│ └─┬ [email protected]
│   └── [email protected] 
├─┬ [email protected]
│ └─┬ [email protected]
│   └── [email protected]  deduped
└─┬ [email protected]
  └─┬ [email protected]
    └── [email protected]  deduped

larssn · 2018-10-23T10:26:17Z

I finally gave up and recreated the entire project.
Fortunately it paid off and I can continue doing actual work.

I ran tns create and then copied over my .git directory.
This greatly simplified the process in my opinion.
(I just hat to revert and diff for a while ...)

I tried the 'sped up version' of your suggestion, basically doing a tns create, copying over the .git folder, and then doing a git reset --hard. The issue still happens when doing that.

mathias-mcb · 2018-10-23T12:54:26Z

I wrestled with the issue for quite some days. Eventually I came up with a little build script that works in my case, at least. Maybe somebody finds it useful:

tns platform clean ios
tns install
tns build ios --bundle --env.uglify
tns prepare ios --release

I basically install from scratch. Afterwards - in xcode - I configure the signing team and I'm able to run the app on my phone and publish it to the app store.

hettiger · 2018-10-24T06:27:03Z

@larssn I did not reset --hard intentionally. Like i said: »I just hat to revert and diff for a while ...«
Probably that's why it did not work for you.

larssn · 2018-10-24T09:54:53Z

We ended up making new provisioning profiles.

hettiger · 2018-10-25T07:02:34Z

@larssn That would have been my last resort too but I wanted to keep using automatic code signing.

jrz · 2018-11-06T13:07:55Z

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

darkyelox · 2018-12-03T16:31:12Z

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.

SephReed · 2019-04-22T19:55:11Z

Has anyone found a solution for this problem yet? None of the above have worked for me.

Alternatively, could anyone please at least explain roughly what's going on? Why is there more than one Provisioning Profile if I only ever created one? How is this other one being found?

This issue is really sucking up my time, and I don't yet even know what the core of the problem is

SephReed · 2019-04-22T20:54:31Z

Creating a new project and copying everything over did the trick for me in the end... :/

Fatme added the question label May 15, 2018

NickIliev added bug os: ios code signing and removed question labels Oct 2, 2018

SephReed mentioned this issue Apr 22, 2019

XCode project: framework not found CocoaLumberjack #4560

Closed

rosen-vladimirov self-assigned this May 13, 2019

rosen-vladimirov added this to the 6.0.0 milestone May 22, 2019

miroslavaivanova closed this as completed Jul 2, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

EXPORT FAILED fse.node has conflicting provisioning settings #3568

EXPORT FAILED fse.node has conflicting provisioning settings #3568

iosdeveloper1001 commented May 8, 2018 •

edited

Loading

willzarem commented May 22, 2018 •

edited

Loading

mathias-mcb commented Jun 28, 2018 •

edited

Loading

NickIliev commented Aug 7, 2018 •

edited

Loading

surdu commented Aug 14, 2018 •

edited

Loading

surdu commented Aug 14, 2018 •

edited

Loading

pajohns commented Aug 28, 2018

surdu commented Aug 29, 2018

iosdeveloper1001 commented Aug 30, 2018 •

edited

Loading

hettiger commented Oct 2, 2018

surdu commented Oct 2, 2018 •

edited

Loading

hettiger commented Oct 2, 2018

surdu commented Oct 2, 2018 •

edited

Loading

hettiger commented Oct 2, 2018

surdu commented Oct 2, 2018 •

edited

Loading

hettiger commented Oct 2, 2018

hettiger commented Oct 4, 2018

jrz commented Oct 17, 2018

jrz commented Oct 17, 2018

jrz commented Oct 17, 2018

jrz commented Oct 17, 2018

larssn commented Oct 23, 2018

larssn commented Oct 23, 2018

mathias-mcb commented Oct 23, 2018

hettiger commented Oct 24, 2018

larssn commented Oct 24, 2018

hettiger commented Oct 25, 2018

jrz commented Nov 6, 2018

darkyelox commented Dec 3, 2018

SephReed commented Apr 22, 2019

SephReed commented Apr 22, 2019

EXPORT FAILED fse.node has conflicting provisioning settings #3568

EXPORT FAILED fse.node has conflicting provisioning settings #3568

Comments

iosdeveloper1001 commented May 8, 2018 • edited Loading

willzarem commented May 22, 2018 • edited Loading

mathias-mcb commented Jun 28, 2018 • edited Loading

NickIliev commented Aug 7, 2018 • edited Loading

surdu commented Aug 14, 2018 • edited Loading

surdu commented Aug 14, 2018 • edited Loading

pajohns commented Aug 28, 2018

surdu commented Aug 29, 2018

iosdeveloper1001 commented Aug 30, 2018 • edited Loading

hettiger commented Oct 2, 2018

surdu commented Oct 2, 2018 • edited Loading

hettiger commented Oct 2, 2018

surdu commented Oct 2, 2018 • edited Loading

hettiger commented Oct 2, 2018

surdu commented Oct 2, 2018 • edited Loading

hettiger commented Oct 2, 2018

hettiger commented Oct 4, 2018

jrz commented Oct 17, 2018

jrz commented Oct 17, 2018

jrz commented Oct 17, 2018

jrz commented Oct 17, 2018

larssn commented Oct 23, 2018

larssn commented Oct 23, 2018

mathias-mcb commented Oct 23, 2018

hettiger commented Oct 24, 2018

larssn commented Oct 24, 2018

hettiger commented Oct 25, 2018

jrz commented Nov 6, 2018

darkyelox commented Dec 3, 2018

SephReed commented Apr 22, 2019

SephReed commented Apr 22, 2019

iosdeveloper1001 commented May 8, 2018 •

edited

Loading

willzarem commented May 22, 2018 •

edited

Loading

mathias-mcb commented Jun 28, 2018 •

edited

Loading

NickIliev commented Aug 7, 2018 •

edited

Loading

surdu commented Aug 14, 2018 •

edited

Loading

surdu commented Aug 14, 2018 •

edited

Loading

iosdeveloper1001 commented Aug 30, 2018 •

edited

Loading

surdu commented Oct 2, 2018 •

edited

Loading

surdu commented Oct 2, 2018 •

edited

Loading

surdu commented Oct 2, 2018 •

edited

Loading