Recent Posts
Archive
- May 2008 (1)
- June 2008 (3)
- July 2008 (3)
- August 2008 (2)
- September 2008 (3)
- October 2008 (3)
- November 2008 (2)
- December 2008 (3)
- January 2009 (2)
- February 2009 (2)
- March 2009 (3)
- April 2009 (2)
- May 2009 (2)
- June 2009 (4)
- July 2009 (2)
- August 2009 (2)
- September 2009 (1)
- December 2009 (1)
- April 2010 (1)
- May 2010 (1)
- June 2010 (2)
- September 2010 (3)
- October 2010 (2)
- December 2010 (1)
- January 2011 (1)
- May 2011 (3)
- June 2011 (1)
- January 2012 (1)
- February 2012 (1)
- April 2012 (1)
- October 2013 (1)
- March 2014 (1)
- June 2014 (1)
- December 2014 (1)
- June 2015 (1)
- November 2015 (1)
- April 2016 (1)
That doesn't sound good. I haven't seen something like this in the current version of the application, but maybe there's something that can trigger it in iOS 5.0. Are you running iOS 5.0?
In any case, was this after a fresh install, or did you do more with the application after your first use? Did you create any equations or equation categories? Did you save any calculations to the recent calculations list?
It's hard to tell what might be going wrong here, but I'll see if I can dig through the reported crash logs on iTunes Connect to find out what might be the cause. I'm working on an update, so if I can determine what's triggering this behavior, I'll get it patched in the next version.
The only immediate fix for this that I can think of is fairly extreme. If you uninstall the application from your iPad, then reinstall it from the App Store (it won't charge you a second time if you go to download it again, because it knows you bought the application already), this should clear out the problematic database. Unfortunately, this will also wipe everything you did in the application, so it will lose your current calculations and saved equations. Only do this if you're willing to lose that data.
In the meantime, I'll work on this and see if I can find a way to fix it. I'm really sorry about that.