Its because a native crash on android crashes the app immediately instead of going up through the java exception handler that crittercism relies on to catch and report the crashes. Its easy enough to pass it back up if we're forcing the crash.
I haven't looked into catching exceptions at a C level on Android, might be possible though.
Amazing indeed! I was already investigating how to pass native errors back to Java but now I can return to focusing on my game. Thus far I have been consistently impressed with the Crittercism team's commitment to their users.