Just in case there’s someone else that didn’t know this, when one gets an error code from one of the iPhone/OS X SDKs with no other information available, it can usually be looked up in the MacErrors.h header. Just open a terminal, type:

open -h MacErrors.h

Then do a search for your error code and you’ll hopefully find a corresponding macro name that gives some indication of what went wrong.

Failing that, if you have an inkling of where the error occurred (eg. the AudioToolbox framework), then you can often find the error defined within the framework’s headers:

That was, type in Terminal grep -r 'the error code', then drag the framework straight from XCode into the Terminal, where the path will be inserted.

Related posts

• Error -12986 and you A customer recently got in touch with me with an...
• Core Audio and freakin’ error -66632 This will only be of interest to a very small...
• Creating applications in XCode using frameworks Defining a proper, logical structure to a new project is...
• The Making of Talkie: Broadcasting Part 1 Talkie is my newest product, the result of...
• Links for June 3rd through June 18th Links for June 3rd through June 18th: Ten logo design...