Code Signing Error: "Unity-iPhone" requires a provisioning profile.

I'm getting an error when trying to archive my project on xcode 9.4

Code Signing Error: "Unity-iPhone" requires a provisioning profile. Select a provisioning profile for the "Release" build configuration in the project editor.
Code Signing Error: Code signing is required for the product type 'Application' in SDK 'iOS 11.4'


I have created a provisioning profile and downloaded it to my computer. According to the apple dev instructions you double click this file and "voila" it's supposed to work. But I'm still receiving these errors. Is there any other way to select a provisioning profile? Thanks

 

What does it say for provisioning profile under General/Signing in the Xcode project?

 

If I go to Preferences > General there is no option for signing there

 

Not preferences - the project.

 

Did you create a development provisioning Profile instead of a distribution one? You can manually sign it and should see available profiles listed

 

I am getting these same errors and have tried what andymads suggested above, but still no go. Trying not to sound like a total newb, but how do I make sure I created the right Profile?? Many thanks!

 

I am trying to build on my iPhone from xCode, and am receiving similar errors.

"error: "Unity-iPhone" requires a provisioning profile. Select a provisioning profile for the "ReleaseForRunning" build configuration in the project editor. (in target 'Unity-iPhone')"

I followed this tutorial ( https://unity3d.com/learn/tutorials/topics/mobile-touch/building-your-unity-game-ios-device-testing) very closely, but am still receiving the error message and "Build Failed".

Any suggestions?

 

can you show what is shown under signing, when you select the project in the project navigator, then select the general tab and then the target Unity-iPhone?
The details for each configuration you can see when you select the tab Build Settings. There is a signing section and you can unfold each property to see the values for each build configuration like ReleaseForRunning

 

hello, I have the same problem and I have an img of my project signing.

 

Hi, I had exactly same issue, I not sure if this is going to help in your case, but it works great for me.


Notice the selected icon in the upper left corner (Projects in xcode).
Select Project in question. Click General Tab in the middle panel.
Notice Signing Expander. Check the checkbox : Automatic manage signing.
When it opens, select team (you should add your apple id to accounts in the xcode preferences).

After selecting the team, that should be it, you can start the build.

 

I got similar problem. When I set provisioning profile and signing team in unity settings, they are getting transferred to Xcode properly, but when I'm trying to build in Xcode it still says

"Showing Recent Issues

"Unity-iPhone" requires a provisioning profile. Select a provisioning profile in the Signing & Capabilities editor."

I see that all I have to do to fix that is go to Signing & Capabilities and Select the same profile that is already selected again (despite it is already selected, it looks like I need to "refresh" it). Is there any solution for that? I know it's not a big deal, it's just one more click when building, but its annoying :/

 

Don't forget to set the team in 'All' under Signing & Capabilities and not just 'Release' or 'ReleaseForProfiling' etc. That will save you pulling out hair as I realised today.

 

OMG! You have saved my day man! Thank you very much!!!

 

A BIG BIG thank you!

 

Same, you just saved my day, I was only looking under the Debug tab! Thanks mate

 

A million Thanks! Been stuck for a whole day

 

Thank you! This community is awesome!

 

This solved My problem, thanks a lot

 

Thank you very very very much

 

That didn’t work setting all the signing why is unity such a mess sometimes not my provision profile unity's I phone provision profile they themselves ain’t much help and who even knowns when they will respond anyway conflicting profiles for unity iPhone

 

Oh goodness. You're a blessing. I was getting frustrated with this for ages and couldn't figure out what it was!

 

I had the same problem. It happened after update from 2020.2.6f1 to 2022.1.0f.
In my case, the cause of the problem is provisioning profile.

I used provisioning name in 2020.2.6f1 and it has no problem, but it doesn't work anymore in 2022.1.0f.

Bad - Do not use name in Profile ID


Good - Use UUID

 

Saved my day, thank you!

 

Saved my day, thank you!