Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

I get conflicting provisioning settings error when I try to archive to submit an iOS app

Tags:

xcode

ios

Now I'm trying to Product>Archive my iOS app to submit. However, I am getting following errors:

AppName has conflicting provisioning settings. AppName is automatically signed for development, but a conflicting code signing identity iPhone Distribution has been manually specified. Set the code signing identity value to iPhone Developer in the build settings editor, or switch to manual signing in the project editor.`

Code signing is required for product type 'Application' in SDK 'iOS 10.1'`

The situation won't change even those I've retry a whole process to recreate iOS certificates or provisioning profile.

I was setting as iOS Distribution in TARGETS > Code Signing Identity > Release > Any iOS SDK. When I changed the setting as iOS Developer here, and changed the setting in PROJECTS > Code Signing Identity > Release > Any iOS SDK as iOS Distribution, I've succeeded in archiving. I'm wondering is it necessary to set as iOS Distribution in the target editor or not. And if it's mandatory, please someone let me know how can I work around this error.

My XCode version is 8.1.

like image 466
vanagar Avatar asked Nov 27 '16 00:11

vanagar


People also ask

What is provisioning file iOS?

The profiles resource represents the provisioning profiles that allow you to install apps on your iOS devices or Mac. You can create and delete provisioning profiles, and download them to sign your code. Provisioning profiles include signing certificates, device identifiers, and a bundle ID.

What does in app provisioning mean?

Application provisioning revolves around mobile app lifecycle management: Preparing, configuring, delivering, and managing mobile apps within an Endpoint Management environment. In some instances, developing or modifying application code might also be part of the provisioning process.


2 Answers

I had this same error, but I had already checked "Automatically manage signing".

The solution was to uncheck it, then check it again and reselect the Team. Xcode then fixed whatever was causing the issue on its own.

like image 94
Erin Geyer Avatar answered Sep 21 '22 13:09

Erin Geyer


I had the same problem, I noticed that If you want to make a release of your iOs app and publish it on the App Store you don't need at all to put in the "Code Signing Identity" as release, just keep it as iOs developer.

Go to Your project -> Build Settings -> Code Signing Identity and put everything to iOs developer.

enter image description here

like image 20
Led Machine Avatar answered Sep 23 '22 13:09

Led Machine