Archive for February 12th, 2010

12
Feb

Script: dsym-archiver

[UPDATE: Xcode 3.2.2 has, apparently, rendered this kind of workaround obsolete. W00t!]

Here’s a possibly handy with a little editing script for use with your iPhone development, which does two things:

This script is intended to be run during an Xcode build to archive your build’s dSYM bundles (needed for symbolicating crash logs received from iTunes Connect or beta testers’ feedback) and, for beta releases, to create an .ipa package to send to your beta testers.

There’s a few path assumptions that probably need fixing for your setup, and it needs to run as a separate target since the binary has to be signed for making an ipa to work, but hey it’s a useful start.

If you’re wondering just why making an .ipa is worth any trouble whatsoever, rumour has it that making an .ipa is an effective way of getting around The Problem That No Doubt You Have Encountered if you do any ad hoc builds for Windows users –That Problem being that the @(#$&@!!! things never work. OK, we exaggerate … but they certainly do cause problems on a regular basis. Personally, we’ve had a good deal of luck remedying that by zipping up our .apps with this fine product,

ZipMacFiles4PC

as it seems that the problem is due to something in the .app folder which sometimes doesn’t get decompressed properly on a Windows machine, and keeping it in .ipa (which is just your .app zipped with some enclosing folders) format through to dropping it on Windows iTunes avoids that. We’ll go to the trouble of checking to see if that is indeed the case next time we run into a complaining Windows user. And perhaps, we’ll even do it without sending first our usual response of “Oh, your problem is very easy to fix. Simply visit your local Apple Store, and BUY YOURSELF A MAC!” since that never really seems to go over all that well, for some strange reason. We certainly don’t understand, it seems a perfectly logical and reasonable solution, don’t you agree?

h/t: iPhoneSDK!