Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Xcode 8 no code signature found

After I upgraded to Xcode 8, I am unable to debug on the device due to the following error:

App installation failed. No code signature found.

My setup, observations and what I've tried so far:

  • The device has iOS 10 installed
  • Code signing and debugging on the device in Xcode 7 works (no changes made to the code signing)
  • The app has a watch app (build/run without watch app didn't change anything)
  • Refreshing provisioning profiles, removing all of them and redownloading them didn't change anything
  • Removing ALL code signing setup from the build settings and enabled "automatically manage signing", which also didn't help
  • I'm always cleaning the build folder
  • I've tried restarting the device, xcode, the mac
  • My colleague reports the same issue with the same project
  • I've tried reverting the changes Xcode 8 suggested (build settings, warning fixes, ...)
like image 338
Martin Polak Avatar asked Sep 18 '16 13:09

Martin Polak


2 Answers


older answer is wrong

I got the same problem here, I have five project, and the four of them can not debug on device and only one can debug on device. I compared the Xcode project files and did not figure it out. I believe it is a provisioning profile issue. it seem that the Xcode will generate the development provisioning profile in your Xcode and did not upload it to your apple developer account.


update:

I finally solve my problem, it seems like a third framework manual set the codesign identity or privisioning profile in the signing seciton of build setting. then you install this third framework, in the codesigning phase, Xcode will search the non-existing codesign identity or privisioning profile for this framework, then it failed.

like image 180
user2031805 Avatar answered Oct 03 '22 17:10

user2031805


I was finally able to solve it with the following:

  • Update carthage (0.18 is currently the latest version). For some reason the code signing was not applied correctly.
  • In build settings set PROVISIONING_PROFILE and PROVISIONING_PROFILE_SPECIFIER both to the same and correct profile
  • I had to disable automatically manage signing

In conclusion, all my provisioning profiles were correct and the problem was only related to code signing the frameworks and not to the app itself. If the error message would have stated where specifically No code signature could have been found, it would have saved quite some debugging time...

like image 39
Martin Polak Avatar answered Oct 03 '22 18:10

Martin Polak