restoroot.com http://www.restoroot.com/Blog Fri, 04 Sep 2009 13:18:13 +0000 http://wordpress.org/?v=2.8.4 en hourly 1 Letter Opener 3 compatibly with Mac OS X 10.6 Snow Leopard http://feedproxy.google.com/~r/restoroot/~3/oOHAmxN71Wc/ http://www.restoroot.com/Blog/2009/09/03/letter-opener-3-compatibly-with-mac-os-x-106-snow-leopard/#comments Thu, 03 Sep 2009 19:09:48 +0000 Christopher Atlan http://www.restoroot.com/Blog/?p=135 Snow Leopard

I’m happy to announce Letter Opener Version 3 for Mac OS X 10.6 Snow Leopard.

Snow Leopard required a complete rewrite of Letter Opener. A big thx here to Scott Morrison of Indev Software for figuring out how to get Mail Plug-ins working in 64-bit mode!

The upgrade is free for everybody who bought Letter Opener after June 8, 2009. For all other users an upgrade is available.

You can download the upgrade from here.


]]> http://www.restoroot.com/Blog/2009/09/03/letter-opener-3-compatibly-with-mac-os-x-106-snow-leopard/feed/ 8 http://www.restoroot.com/Blog/2009/09/03/letter-opener-3-compatibly-with-mac-os-x-106-snow-leopard/ Five Star Rating from Macworld http://feedproxy.google.com/~r/restoroot/~3/3rDgbT-ePaI/ http://www.restoroot.com/Blog/2009/05/31/five-star-rating-from-macworld/#comments Sun, 31 May 2009 18:52:37 +0000 Christopher Atlan http://www.restoroot.com/Blog/?p=130 Macworld

Just to get your product mentioned in Macworld is a great bless, but to get a five star rating is a real tribute. Deborah Shadovitz did the review, here’s a quote from it:

With Letter Opener in Apple Mail, the worry is gone. Letter Opener converts winmail.dat files on the fly, so you can actually see and use what the sender intended you to have. There’s no fuss with Letter Opener, no need to drag the winmail.dat file onto another application or call upon several programs to help you. Once Letter Opener is installed, you can forget about it.

The pricing is always a tricky thing, so I was especially happy to read this:

If you regularly receive winmail.dat files from business associates, Letter Opener is well worth the investment.

You can read the full article here.

]]> http://www.restoroot.com/Blog/2009/05/31/five-star-rating-from-macworld/feed/ 0 http://www.restoroot.com/Blog/2009/05/31/five-star-rating-from-macworld/ AudioSessionInitialize Workarounds http://feedproxy.google.com/~r/restoroot/~3/U0Eip1HGufo/ http://www.restoroot.com/Blog/2008/12/25/audiosessioninitialize-workarounds/#comments Thu, 25 Dec 2008 19:17:44 +0000 Christopher Atlan http://www.restoroot.com/Blog/?p=118 Core Audio

Yesterday I decided to go after one of my audio bugs by take a look how AVAudioPlayer does it right, and I discovered a little thing about Audio Session.

Here are two workarounds for AudioSessionInitialize.

I never liked AudioSessionInitialize because you can set the InterruptionListener and it’s ClientData just once:

/*
 * Discussion
 * Your application must call this function before making any other Audio
 * Session Services calls. You may activate and deactivate your audio session
 * as needed (see AudioSessionSetActive), but should initialize it only once.
 */
OSStatus AudioSessionInitialize (
   CFRunLoopRef                        inRunLoop,
   CFStringRef                         inRunLoopMode,
   AudioSessionInterruptionListener    inInterruptionListener,
   void                                *inClientData
);

So you need a helper class like this where you have to set the active AudioPlayer:

#import "AudioInterruptionListener.h"

void interruptionListenerCallback (
                                   void *inUserData,
                                   UInt32   interruptionState
) {
    AudioInterruptionListener *listener = (AudioInterruptionListener *) inUserData;
    DoItYourselfPlayer *player = listener.doItYourselfPlayer;
    
    if (!player)
        return;
    
    if (interruptionState == kAudioSessionBeginInterruption) {
        [player performSelectorOnMainThread:@selector(audioStreamPlayerBeginInterruption)
                                 withObject:nil
                              waitUntilDone:YES];
    } else if ((interruptionState == kAudioSessionEndInterruption)) {
        [player performSelectorOnMainThread:@selector(audioStreamPlayerEndInterruption)
                                 withObject:nil
                              waitUntilDone:YES];
    }
}

@implementation AudioInterruptionListener

static AudioInterruptionListener *sharedAudioInterruptionListener;

@synthesize doItYourselfPlayer;

+ (void)initialize {
    if (!sharedAudioInterruptionListener) {
        sharedAudioInterruptionListener = [[AudioInterruptionListener alloc] init];
        AudioSessionInitialize (
                                NULL,
                                NULL,
                                interruptionListenerCallback,
                                sharedAudioInterruptionListener
                                );
    }
}

+ (AudioInterruptionListener *)sharedAudioInterruptionListener
{
    return sharedAudioInterruptionListener;
}

@end

This is fine, but I was no big fan of this helper class when I wrote it.

AVAudioPlayer works without such helper class, but how? Well don’t do this at home, because ‘intr’ is not documented in “Audio Session Services Property Identifiers.”, but you can also add an InterruptionListener with AudioSessionAddPropertyListener, the code should look something along this lines:

- (BOOL)prepareToPlay {
    pthread_once(&interruptionListenerOneTimeInit, interruptionListenerInit);
    …
    AudioSessionAddPropertyListener(’intr’, interruptionListenerCallback, self);
}

- (void)stop {
    AudioSessionRemovePropertyListenerWithUserData(’intr’, interruptionListenerCallback, self);
    …
}

#pragma mark -
#pragma mark Audio Session Implementations

pthread_once_t          interruptionListenerOneTimeInit = PTHREAD_ONCE_INIT;

void interruptionListenerInit(void)
{
    AudioSessionInitialize(NULL, NULL, NULL, NULL);
}

void interruptionListenerCallback (
                                    void                      *inClientData,
                                    AudioSessionPropertyID    inID,
                                    UInt32                    inDataSize,
                                    const void                *inData
) {
    DoItYourselfPlayer *player = inClientData;
    if (inID == ‘intr’) {
        UInt32 *interruptionState = (UInt32 *)inData;
        
        if (*interruptionState == kAudioSessionBeginInterruption) {
              [player performSelectorOnMainThread:@selector(audioStreamPlayerBeginInterruption)
                                 withObject:nil
                              waitUntilDone:YES];
        } else if (*interruptionState == kAudioSessionEndInterruption) {
              [player performSelectorOnMainThread:@selector(audioStreamPlayerEndInterruption)
                                 withObject:nil
                              waitUntilDone:YES];
            }
        }
    }
}

If you agree that Apple should expose this functionality to third parties, please submit a duplicate for Radar ID# 6467253.

Happy Holidays hacking!

]]> http://www.restoroot.com/Blog/2008/12/25/audiosessioninitialize-workarounds/feed/ 0 http://www.restoroot.com/Blog/2008/12/25/audiosessioninitialize-workarounds/ Letter Opener 2.0.7 compatible with Mac OS X 10.5.6 http://feedproxy.google.com/~r/restoroot/~3/LA91QX6Ok_s/ http://www.restoroot.com/Blog/2008/12/15/letter-opener-207-compatible-with-mac-os-x-1056/#comments Mon, 15 Dec 2008 19:45:19 +0000 Christopher Atlan http://www.restoroot.com/Blog/?p=113 Letter Opener -> Check for updates…), or download Letter Opener 2.0.7 here. Troubleshooting Document: Mac OS X 10.5.6: [...]]]> bundle.png

Apple has changed Mail in the today released Mac OS X 10.5.6 which results in a crash if you have Letter Opener installed. An updated version is already available.

Please use the build-in update function (Mail Menu -> Letter Opener -> Check for updates…), or download Letter Opener 2.0.7 here.

Troubleshooting Document: Mac OS X 10.5.6: Mail unexpectedly quits (TS2486).


]]> http://www.restoroot.com/Blog/2008/12/15/letter-opener-207-compatible-with-mac-os-x-1056/feed/ 7 http://www.restoroot.com/Blog/2008/12/15/letter-opener-207-compatible-with-mac-os-x-1056/ Apple Mail Plugins Developer Group http://feedproxy.google.com/~r/restoroot/~3/I7Opp7Mbd6I/ http://www.restoroot.com/Blog/2008/12/12/apple-mail-plugins-developer-group/#comments Fri, 12 Dec 2008 18:39:14 +0000 Christopher Atlan http://www.restoroot.com/Blog/?p=109 bundle.png

After talking with Scott Morrison of Indev Software at C4[2] about a mail list for Mail Plugin developers we finally started one.

If you are interested in this topic you are welcome to join us: Google Groups – Apple Mail Dev




]]> http://www.restoroot.com/Blog/2008/12/12/apple-mail-plugins-developer-group/feed/ 1 http://www.restoroot.com/Blog/2008/12/12/apple-mail-plugins-developer-group/ Crash Reporter for iPhone Applications (Part 2) http://feedproxy.google.com/~r/restoroot/~3/18GxLUoSXdE/ http://www.restoroot.com/Blog/2008/10/20/crash-reporter-for-iphone-applications-part-2/#comments Mon, 20 Oct 2008 22:07:43 +0000 Christopher Atlan http://www.restoroot.com/Blog/?p=83 crashDuck.png

In part one I describe how to set up an Exception Handler, Uli discovered as first one that this handles not all cases. The missing part is a signal handler to get information of SIGSEGV, SIGBUS, … signals.

I thought the hard part of this is getting the backtrace inside a signal handler. I already found code for this, but I couldn’t use it because it was GPL. I tried the easy way, offering the author money to release it under public domain, oh boy this was a waste of time. But now that I found my own solution for this I’m happy that I didn’t spend money on this. (1 line versus 20 lines of code)

Let’s start with setting up a signal handler, the good old man page helps.

  1. int main(int argc, char *argv[]) {
  2.         struct sigaction mySigAction;
  3.         mySigAction.sa_sigaction = mysighandler;
  4.         mySigAction.sa_flags = SA_SIGINFO;
  5.         sigemptyset(&mySigAction.sa_mask);
  6.         sigaction(SIGQUIT, &mySigAction, NULL);
  7.         sigaction(SIGILL, &mySigAction, NULL);
  8.         sigaction(SIGTRAP, &mySigAction, NULL);
  9.         sigaction(SIGABRT, &mySigAction, NULL);
  10.         sigaction(SIGEMT, &mySigAction, NULL);
  11.         sigaction(SIGFPE, &mySigAction, NULL);
  12.         sigaction(SIGBUS, &mySigAction, NULL);
  13.         sigaction(SIGSEGV, &mySigAction, NULL);
  14.         sigaction(SIGSYS, &mySigAction, NULL);
  15.         sigaction(SIGPIPE, &mySigAction, NULL);
  16.         sigaction(SIGALRM, &mySigAction, NULL);
  17.         sigaction(SIGXCPU, &mySigAction, NULL);
  18.         sigaction(SIGXFSZ, &mySigAction, NULL);
  19.        
  20.         NSAutoreleasePool * pool = [[NSAutoreleasePool alloc] init];
  21.         int retVal = UIApplicationMain(argc, argv, nil, nil);
  22.         [pool release];
  23.         return retVal;
  24. }

And here the line of code I was searching for over two days: backtrace(3). You don’t find this little bastard if you search in Xcode Help with iPhone OS Library selected (there goes my two days)

  1. void mysighandler(int sig, siginfo_t *info, void *context) {
  2.         void *backtraceFrames[128];
  3.         int frameCount = backtrace(backtraceFrames, 128);
  4.  
  5.         // report the error
  6. }

Like in the Exception Handler you now just use backtrace_symbols(3). (Example)

Good luck with working down the crash reports you will get now :)

Crash Reporter for iPhone Applications (Part 1)
Crash Reporter for iPhone Applications (Part 2)


]]> http://www.restoroot.com/Blog/2008/10/20/crash-reporter-for-iphone-applications-part-2/feed/ 4 http://www.restoroot.com/Blog/2008/10/20/crash-reporter-for-iphone-applications-part-2/ Crash Reporter for iPhone Applications (Part 1) http://feedproxy.google.com/~r/restoroot/~3/8wSeJJ1Kmz0/ http://www.restoroot.com/Blog/2008/10/18/crash-reporter-for-iphone-applications/#comments Sat, 18 Oct 2008 18:58:14 +0000 Christopher Atlan http://www.restoroot.com/Blog/?p=59 crashDuck.png

I’m getting ready to send my iPhone Application to the first beta testers and so I started thinking about crash reports.

On the Mac you have two options to get the crash report of your application. The first one is to check on startup if there is a new crash report file in ~/Library/Logs/CrashReporter for your application and simply send it. (Example: HDCrashReporter , UKCrashReporter)

The other option is to use NSExceptionHandler, which let you report the problem as it happens. (Example: A simple debugging tool for Cocoa)

On the iPhone you can’t access the crash report file form your application because it’s running in a sandbox (rdar://problem/6296554). iTunes synchronizes the crash reports of all applications, so although a user could in theory send it to you, this seems rather complicated to me (Locations of Crash Logs).

So what about NSExceptionHandler? Well, there isn’t a NSExceptionHandler in the iPhone SDK. But wait, there is a NSUncaughtExceptionHandler!

  1. void MyUncaughtExceptionHandler(NSException *exception) {
  2.     NSArray *callStackArray = [exception callStackReturnAddresses];
  3.     int frameCount = [callStackArray count];
  4.     void *backtraceFrames[frameCount];
  5.    
  6.     for (int i=0; i<frameCount; i++) {
  7.         backtraceFrames[i] = (void *)[[callStackArray objectAtIndex:i] unsignedIntegerValue];
  8.     }
  9.    
  10.     // report the exception
  11. }
  12.  
  13. @implementation AppDelegate
  14.  
  15. - (void)applicationDidFinishLaunching:(UIApplication *)application {
  16.     NSSetUncaughtExceptionHandler(&MyUncaughtExceptionHandler);
  17. }
  18.  
  19. @end

Now you can get the backtrace in MyUncaughtExceptionHandler with backtrace_symbols(3). (Example)
You still have to symbolicate the crash reports.

As a big fan of Fogbugz, I also wanted to use BugzScout. It’s just a HTTP POST, but here is the code:

  1. void bugzScout(NSString *description, NSString *extra) {
  2.         NSMutableString *post = [NSMutableString string];
  3.         [post appendString:@"ScoutUserName="];
  4.         [post appendString:urlEncodeValue(@"Your BugzScout User")];
  5.        
  6.         [post appendString:@"&ScoutProject="];
  7.         [post appendString:urlEncodeValue(@"Your Project")];
  8.        
  9.         [post appendString:@"&ScoutArea="];
  10.         [post appendString:urlEncodeValue(@"Your Area")];
  11.        
  12.         [post appendString:@"&Description="];
  13.         [post appendString:urlEncodeValue(description)];
  14.        
  15.         [post appendString:@"&Extra="];
  16.         [post appendString:urlEncodeValue(extra)];
  17.        
  18.         [post appendString:@"&ScoutDefaultMessage=&FriendlyResponse=0&ForceNewBug=0"];
  19.        
  20.         //NSLog(post);
  21.        
  22.         NSData *postData = [post dataUsingEncoding:NSASCIIStringEncoding allowLossyConversion:YES];
  23.         NSString *postLength = [NSString stringWithFormat:@"%d", [postData length]];
  24.        
  25.         NSURL *webServiceURL = [NSURL URLWithString:@"https://yourcompany.fogbugz.com/ScoutSubmit.asp"];
  26.         NSMutableURLRequest *req = [NSMutableURLRequest requestWithURL:webServiceURL];
  27.        
  28.         [req setHTTPMethod:@"POST"];
  29.         [req addValue:@"application/x-www-form-urlencoded" forHTTPHeaderField: @"Content-Type"];
  30.         [req addValue:postLength forHTTPHeaderField: @"Content-Length"];
  31.         [req setHTTPBody:postData];
  32.        
  33.         [NSURLConnection sendSynchronousRequest:req returningResponse:nil error:nil];   
  34. }
  35.  
  36. NSString *urlEncodeValue(NSString *str) {
  37.         CFStringRef urlString = CFURLCreateStringByAddingPercentEscapes(kCFAllocatorDefault,
  38.                 (CFStringRef)str, NULL, CFSTR(";/?:@&=+$,"), kCFStringEncodingUTF8);
  39.         return [(NSString *)urlString autorelease];
  40. }

Crash Reporter for iPhone Applications (Part 1)
Crash Reporter for iPhone Applications (Part 2)

]]> http://www.restoroot.com/Blog/2008/10/18/crash-reporter-for-iphone-applications/feed/ 12 http://www.restoroot.com/Blog/2008/10/18/crash-reporter-for-iphone-applications/ OMiC Version 2.0 Beta 6 (Leopard ready) http://feedproxy.google.com/~r/restoroot/~3/wC-MfWSty1A/ http://www.restoroot.com/Blog/2008/07/31/omic-version-20-beta-6-leopard-ready/#comments Thu, 31 Jul 2008 13:06:21 +0000 Christopher Atlan http://www.restoroot.com/Blog/?p=54 OMiC -> Check for updates…), else just write me [...]]]> bundle.png

Beta 6 support winmail.dat files in encrypted messages, improved winmail.dat file recognition, and as always bug fixes.

Note: The last two betas include sparkle 1.5b4 and there are still some problems with that.

If you already using the beta, please use the build-in update function (Mail Menu -> OMiC -> Check for updates…), else just write me a line.

By the way, I’m try to get into this twitter thing, so if you like you can follow me.

]]> http://www.restoroot.com/Blog/2008/07/31/omic-version-20-beta-6-leopard-ready/feed/ 129 http://www.restoroot.com/Blog/2008/07/31/omic-version-20-beta-6-leopard-ready/ OMiC Version 2.0 Beta 5 (Leopard ready) http://feedproxy.google.com/~r/restoroot/~3/qGs6zr3eI2s/ http://www.restoroot.com/Blog/2008/07/09/omic-version-20-beta-5-leopard-ready/#comments Wed, 09 Jul 2008 17:38:30 +0000 Christopher Atlan http://www.restoroot.com/Blog/index.php/2008/07/09/omic-version-20-beta-5-leopard-ready/ bundle.png

This beta version fine tune the new integration into Mail. Also the winmail.dat converter itself got lot of bug fixes.

It took again a long time to release this beta, one of the main show stopper is the still existing GMail IMAP issue.

If you already using the beta, please use the build-in update function (Mail Menu -> OMiC -> Check for updates…), else just write me a line.

]]> http://www.restoroot.com/Blog/2008/07/09/omic-version-20-beta-5-leopard-ready/feed/ 12 http://www.restoroot.com/Blog/2008/07/09/omic-version-20-beta-5-leopard-ready/ Google GMail and winmail.dat files http://feedproxy.google.com/~r/restoroot/~3/6Ct5lePNVMU/ http://www.restoroot.com/Blog/2008/06/28/google-gmail-and-winmaildat-files/#comments Sat, 28 Jun 2008 20:29:02 +0000 Christopher Atlan http://www.restoroot.com/Blog/index.php/2008/06/28/google-gmail-and-winmaildat-files/ googlemail.gif

If you are using googles popular mail services GMail over IMAP and demand on winmail.dat files you will run into a problem.

GMail IMAP doesn’t return the senders original winmail.dat file, it return a home-cooked file which have only the name in common. In this case, not even Microsoft Outlook can handle the winmail.dat file.

I tried to contact google about this issue over many different ways, but didn’t get a answer.

There are two workarounds: Switch back to GMail POP3 or use GMail web interface to access mails with winmail.dat attachment.

]]> http://www.restoroot.com/Blog/2008/06/28/google-gmail-and-winmaildat-files/feed/ 7 http://www.restoroot.com/Blog/2008/06/28/google-gmail-and-winmaildat-files/