How to symbolicate crash reports

I written up a short guide on how to symbolicate crash reports. RoboVM strips debug info so crash reports often don’t give much info on where a crash actually occurred and the calls leading up to it. By symbolicating the report more info will be revealed. NOTE: In order to symbolicate a crash report from your published application you must keep the .app and .app.dSYM folders that get created when you generate an IPA file. Here’s the guide: https://github.com/robovm/robovm/wiki/Symbolicate-a-crash-reports

RoboVM 0.0.9 has been released

Today I have the pleasure to announce that version 0.0.9 of RoboVM has been released. Here are the most important changes: Apple recently changed their guidelines to require all new apps submitted to App Store to be built using the tools included in Xcode 5.0.2 or later. RoboVM will now set the DTXcode and DTXcodeBuild values in the Info.plist file properly to meet Apple’s new requirements. Bro has been updated and now supports “machine sized” float and integer types. Using this feature it will be possible to map CocoaTouch types like CGFloat and NSInteger which have different bit sizes on 32-bit and 64-bit targets. System properties can now...