{"id":85,"date":"2011-12-02T01:39:35","date_gmt":"2011-12-02T09:39:35","guid":{"rendered":"http:\/\/michael.lavaveshkul.com\/blog\/?p=85"},"modified":"2019-02-03T00:02:37","modified_gmt":"2019-02-03T08:02:37","slug":"xcodebuild-exit-code-65","status":"publish","type":"post","link":"https:\/\/michael.lavaveshkul.com\/blog\/2011\/12\/xcodebuild-exit-code-65\/","title":{"rendered":"xcodebuild: exit code 65"},"content":{"rendered":"\n

Note: This is from a long time ago and I haven’t really touched this stuff since around the time I wrote this. The information may be out of date. That said, if this does or doesn’t work for you, let me know and I’ll update this with the relevant info.<\/strong><\/p>\n\n\n\n

This is something I ran into a while back. If you’re not an iOS developer, but get tasked with building iOS apps, you may run into this. This particular exit code is fun because xcodebuild doesn’t tell you what the problem is.<\/p>\n\n\n\n

Aside from building your app using the Xcode IDE, you also have the command line utility xcodebuild<\/a> available to you. Assuming the code itself compiles just fine, this tool will tell you, for example, if you’re missing a provisioning profile or something.<\/p>\n\n\n\n

When getting code 65, the build would fail with no explanation in the log. Rather, at the end it would say something like
<com.apple.tools.product-pkg-utility> \"\/Users\/[me]\/Library\/MobileDevice\/Provisioning Profiles\/12345678-ABCD-1234-ABCD-1234567890AB.mobileprovision\" -o \"\/[my_project_build_location]\/embedded.mobileprovision\"
\n*** BUILD FAILED ***<\/code><\/p>\n\n\n\n\n\n\n\n

In my case, it turned out xcodebuild didn’t have access to the certificate I was using.
So… here’s some things to check for:<\/p>\n\n\n\n