question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

EXPORT FAILED fse.node has conflicting provisioning settings

See original GitHub issue

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

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:7
  • Comments:30 (1 by maintainers)

github_iconTop GitHub Comments

4reactions
surducommented, Oct 23, 2018

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)

4reactions
NickIlievcommented, Aug 7, 2018

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

Read more comments on GitHub >

github_iconTop Results From Across the Web

fse.node and terminal-notifier.app… | Apple Developer Forums
I am 2 errors after archive is successfully done, during the Upload process. fse.node has conflicting provisioning settings: fse.node is automatically signed ...
Read more >
I get conflicting provisioning settings error when I try to archive ...
App has conflicting provisioning settings. App is automatically signed, but provisioning profile 'ID' has been manually specified.
Read more >
Xcode Has Conflicting Provisioning Settings - ADocLib
UnityiPhone has Conflicting Provisioning Settings in XCode 1.Select the top level node called UnityiPhone in the left tree view the one with the....
Read more >
Dell EMC OpenManage Enterprise-Modular Edition for ...
Setting up chassis. ... OME–Modular is supported on the following web browsers: ... nodes command on the IOM CLI and check if the...
Read more >
nativescript/CHANGELOG.md - UNPKG
In case you are using such Node.js version, CLI will not allow you to execute any command, ... EXPORT FAILED fse.node has conflicting...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found