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)
Sorry to hear that. What device and iOS version was this happening under? Do you recall what calculation you had been performing when it started crashing?
Unfortunately, the only way to recover from this, short of waiting for the next update, is to delete the application from your device and reinstall it from the App Store (you won't be charged a second time if you choose to download it again). However, this will delete your local library of stored equations and start fresh with the application.
I thought that I had completely eliminated this class of crash, because no one had reported it for over a year. It appeared to be due to database corruption, and I've done everything I can to prevent any of the conditions that triggered this from occurring. I wonder if something new in the OS is allowing this to happen again, although you're the first one to report this.
Again, I'm sorry, but I can't think of a better way to recover from this repeated crashing than starting from a clean install.