I started using the lovely json-framework for the iPhone but then suddenly found that if I compiled for anything greater than 2.1 for a device, that it would pop up with:
Codesign error: “object file format invalid or unsuitable”
It took me a long time to figure out what was going on, but thanks to a blog post, the fix is this:
On the project settings, on the build tab, search for “Code Signing Resource Rules Path” and set “$(SDKROOT)/ResourceRules.plist” as its value.
I’m not sure how it works as it looks like that is the path it already has, but hey, it seems to work!
Thank you, I appreciate you posting this regardless of how simple it is. I don’t understand it either, but you saved me, so thank you
Wow man! I cannot believe what a luck I had finding this post in just one googling… Otherwise it could had taken me ages to figure this out… Thx!!!!
[...] – “object file format invalid or unsuitable” « Matt Galloway’s iPhone Apps JSON Framework Codesign – “object file format invalid or unsuitable” « Matt Galloway’s … [...]
THANK YOU
Thank you, Thank you, Thank you!
Thank you for posting this simple, yet very helpful solution.
Moritz
[...] to some google searching and a blog post by matt galloway, i figured it out. here’s what to [...]
thank you so much for this. so lucky i stumbled upon this link
Hei man, you save me
Thanks a lot man, very helpful
Thanks! This fixed my issue as well.
thanks so much…u saved me too!!
[...] So, to get it installed, follow the Option 2 in the json-framework install instructions, then reset the compiler to gcc 4.2 this is a key point, somehow adding the framework breaks this and you start getting all sorts of strange errors. Then finally you need to add the SDKs code signing resource rules ($(SDKROOT)/ResourceRules.plist) to the code signing resource rules pat… [...]
Awesome, same problem, same solution. Thanks!!!
IT WORKED!!! Thanks. I only lost half of my day!
Perfect!
I could build and deploy old and new apps except for one pesky app. This fixed it.
I totally agree what it do I would like to know but i sure worked, magic, thanks a lot
I found that this worked, but only for the first build after it was changed. Subsequent builds failed unless the change was re-done!
Thanks a ton dude….awesome solution
The linked blog post has vanished.
And this fix doesn’t seem to work any more
.
Hmmm that’s strange that it doesn’t work anymore for you. What version of the SDK are you compiling for?
I might switch over to TouchJSON at some point anyway to be honest – have you tried that?
Holy crap! Thank you! Same problem, banging my head against the private key / provisioning / certificate wall for hours. We had this setting correct in our debug config but forgot to set it for our distribution config.
You saved my Thanksgiving, and many other things. Thanks again!
The fix worked for me, thanks a lot! I got this problem after changing the product name of my app.
you just saved me about 1 week.