[Resolved] Create iOS build broken?

Getting Started Newbie Questions
#1

Tried to make a build today, and I’m getting a problem with code signing:
warning: Application failed codesign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an iPhone Distribution Certificate. (-19011)
failed to extract requirements data: 1
/Users/Oaf/Desktop/LittleBird.app: invalid signature (code or signature have been modified)
failed to extract entitlements: 1
AssertMacros: entitlements_requested, At least need an application-identifier entitlements file: /SourceCache/codesign_wrapper_Sim/Security-1245/codesign_wrapper/codesign_wrapper.c, line: 866

  • (null)

warning: Unable to extract codesigning entitlements from your application. Please make sure LittleBird is a valid Mach executable that’s properly codesigned. (-19050)
/Users/Oaf/Desktop/LittleBird.app/LittleBird: invalid signature (code or signature have been modified)

  • (null)
    So, I deleted the provision profile, and created a new one from scratch - new app id, new bundle name, new adhoc cert, everything. Still doesn’t work.

Is the build server broken?

Thanks,

M [import]uid: 276 topic_id: 25415 reply_id: 325415[/import]

#2

Tried the same app id etc with a Dev cert, and it works… [import]uid: 276 topic_id: 25415 reply_id: 102642[/import]

#3

Sounds like a cert problem, then - the build server was fine. Glad you got this resolved either way :slight_smile: [import]uid: 52491 topic_id: 25415 reply_id: 102673[/import]

#4

It’s not resolved - it doesn’t work with adhoc certs.

I’ve built the cert from scratch, so I can’t see how the cert itself can be at fault - XCode reports it as valid. [import]uid: 276 topic_id: 25415 reply_id: 102674[/import]

#5

Thought I’d try the cert on an existing XCode project, to see if it worked - it didn’t!

It helpfully reported that I had two keychain entries for iPhone Distribution: , fired up KeyChain Access and sure enough, there they were.

Deleted the older one, and everything is working again :slight_smile:

Marked as Resolved :slight_smile:

M
[import]uid: 276 topic_id: 25415 reply_id: 102676[/import]

#6

Sorry, I misunderstood your post above and took it as resolved.

Keychains can be quite a pain :wink: [import]uid: 52491 topic_id: 25415 reply_id: 102761[/import]

#7

Just confirming, had the same problem, and indeed, there were expired certs in Keychain Access, deleting them fixed it. [import]uid: 143026 topic_id: 25415 reply_id: 103808[/import]

#8

Another confirm here! This one really kicked my butt.

I already spent a good while on buying/installing Lion, when from one day to the next I couldn’t continue working on my Corona app. Then Lion wouldn’t install due to a bug with a Windows/BC partition I have (a common thing I’d guess), which was “fixed” via simply creating another 2GB partition. Thanks Google!)

Then I spent a while re-doing expired certs and still nothing seemed to work until I read this thread! Deleting the expired certs did indeed work! THANKS! <8

Really annoying to lose an entire work day over stuff like this, especially without warning and without any realistic options aside from paying Apple to upgrade, and then still getting bogged down by bugs. GRRR! :frowning:

I always thought M$ was pretty evil, but it’s getting hard to tell the difference here lately.

Power corrupts. Absolute power corrupts absolutely.

MOO!
[import]uid: 20929 topic_id: 25415 reply_id: 113831[/import]

#9

Like the “MOO!” sign off :smiley:

Glad you got this resolved eventually, even if it was a right pain at first >.