Updated to Xcode 6.4 and code signing broke

Question

Created Jul ’15

Replies 4

Boosts 0

Views 3.7k

Participants 4

Ok, so, first off, I apologize for my attitude but I spent many hours going through the nightmare of getting dev and production certificates working for my app only a day ago and everything broke just because I updated my Xcode from 6.3.2 to 6.4 so I could test an app on a device updated to iOS 8.4. I'm pretty annoyed and ******.

Anyway, as soon as the xcode update was complete, my code, which was working perfectly, now gives these errors when I try to run on my phone (8.3) or ipad (8.4) but works fine when put on the simulator:

Check dependencies

Code Sign error: ad hoc code signing not allowed with SDK 'iOS 8.4'

CodeSign error: code signing is required for product type 'Unit Test Bundle' in SDK 'iOS 8.4'

I did not change anything with the signing but have since tried every combination of the dev and production certificates I have. I am trying to test on my devices and need to continue to push new builds to beta testers on TestFlight but I'm completely stuck...

Boost

Answer 1

Vanson OP

Jul ’15

This issue needs to be confirmed

0

Answer 2

booksix OP

Jul ’15

I fixed the issue after finding a Stack Overflow post with a ton of random things to try:

1. Goto: Product > Scheme > Edit Scheme...

2. Select "Build" in the left pane

3. Deselect all items in the "<myApp> Tests" row (aside from those one cannot deselect)

4. Click Close button

I have no idea why this worked or what problems it may cause in the future but I'm atleast writing code again. I'm still really annoyed this issue came up and would like more information from Apple...

0

Answer 3

ilboued OP

Jul ’15

I had exactly the same error as you but not from the same 'path' : I was working on a project with 2 targets (ios and osx, with common swift files)... and had the same error message after a couple of modification in my work. Your tips solved my problem too.. but as you I wonder why, and no idea of future consequences...

0

Answer 4

carlile OP

Mar ’16

This fixed the issue for me after I upgraded to Xcode 7.3. So, thanks!

0