Crash on startup

Forums: 

I submitted the Android crash report, but not knowing whether those reports are any good I will post here.

On Samsung Galaxy Tab 2 10.1 running Android 4.1.2, not rooted. I installed Dubscript b45 from the Play Store.

When starting the app, a white screen is loaded with a green title bar containing the logo and the word Dubscript in the top left corner. Nothing happens and after a few seconds the app crashes and up pops the "Unfortunately, DubScript has stopped." box. I have tried reinstalling and the same occurs, as with running whilst connected to WiFi and not. I have closed all apps in the task manager and have cleared the memory in RAM manager.

Bluetooth is turned off as is gps and screen rotation. Battery is over 80% full and I have also tried whilst on charge.

I think that just about covers everything. Please let me know if you need any more information. Would love to see a solution.
Thanks.

I just checked the logs of crash reports and noticed this- I assume it's from you:

Crashes on startup every time. Have cleared memory usage, reinstalled, etc, and still crashes. Loads up white screen with green title bar, then crashes after a few seconds.

I searched through the crash and found this:

Caused by: java.lang.NumberFormatException: Invalid int: "12.0sp"
at java.lang.Integer.invalidInt(Integer.java:138)

This appears to be a problem with how Samsung's version of Android is interpreting the default editing size (12 points) for the font. I just did a search through the code for "12.0sp" and couldn't find any reference to it.

A new version is coming out (barring any major obstacles) in about a week-- it's being compiled by the latest Android build tools and hopefully (?) will fix this issue... so stay tuned. Just to be sure, I'm going to be sure to try re-building it and testing on 4.1.2 (which I think is Jellybean, revision 2...) in the emulator... I hope it fixes the issue.

If you drop me an email, I could possibly arrange to get you an advanced "beta" of the beta to test out a newer version, presuming it doesn't make it to the play store first :)

Quick followup-- I couldn't find an official Android version 4.1.2 -- as you can see here in the official documentation, there is a version 4.1.1 and then it goes straight to version 4.2.

What I did is create a build using API 16 (4.1.1) and tried running it in the emulator. It seems to work great, so look forward to a new build very soon that hopefully will fix whatever problem this was....

Thanks again for the crash report. It really helps!