Selecting game causes app to crash

[GoogleCodeExporter]

[Please glance at the existing issues to make sure the problem you are
reporting  isn't a known issue before reporting.  Feel free to remove or
edit any parts of the form template which don't apply to your issue.]

What steps will reproduce the problem?
1.open app in iPhone 
2.select game
3.subsequent crash every time

What version of Frotz are you using?
1.7

What device model are you using (e.g., iPhone 5, iPhone 3GS, iPad 4, iPod
Touch 4th gen.)
iPhone 5S

What version of iOS?  6.1, 7.0, etc.)
7.1

Please provide any additional information below.

Original issue reported on code.google.com by solark...@gmail.com on 24 Aug 2014 at 1:01

[GoogleCodeExporter]

Hi solarkite!  Are you the person who mentioned this crash in a review on 
iTunes?

I think there's something peculiar about your situation and I hope you will 
help me try to diagnose the problem.

I certainly tested iOS 7.1 on iPhone 5S, being the latest non-beta iOS and most 
current device (as well as others), and Frotz isn't crashing like this for 
everyone.  Apple wouldn't have even approved the app if it crashed that easily.

How much free storage does your phone have?  I'm wondering if it ran out of 
flash storage space during installation upgrade and corrupted something.
Is also possible it is running out of RAM and crashing due to other apps 
running (although I haven't seen this type of problem in a while).

Can you try rebooting your phone (hold down lock button for a few secs), and 
see if Frotz works then?
If that doesn't work you might try reinstalling the app.

There aren't any crash reports in Apple's crash reporter yet, so either this 
issue is rare or there's a long delay in processing before they show up. 

You might have a crash report on your phone you can send me which would help.  
Go to Settings app, then General / About / Diagnostics & Usage / Diagnostics & 
Usage Data.
There hopefully will be one or more crash logs there labeled with "Frotz" and 
the date.
If you do see log(s) for Frotz, you can either:
1) copy and paste the contents of one and email then to ifrotz at gmail.com
2) Turn on Automatic Sending of crash reports on the Diagnostic & Usage page 
and crash Frotz again 
3) Tell me if you sync your iPhone to Mac or PC and I can help you locate the 
crash report there so you can email it

Thanks for any help you can provide in figuring this out! I definitely don't 
want to leave this issue out there unresolved, and will push out an update as 
soon as we figure it out if there's not an easy workaround.

Original comment by spath...@gmail.com on 24 Aug 2014 at 3:34

[GoogleCodeExporter]

(You can paste crash log contents here too, but I thought emailing might be 
easy to do from the device itself).

Original comment by spath...@gmail.com on 24 Aug 2014 at 3:38

[GoogleCodeExporter]

Hi,
I reinstalled the app and that did the trick.
Frotz is now working.
I did not post a review about the problem with this version. I try to
contact the developer before resorting to reviews.  I will be giving a
great review again for this wonderful service you provide as a labor of
love for the art of IF.
Best
James

Original comment by solark...@gmail.com on 24 Aug 2014 at 5:31

[GoogleCodeExporter]

Awesome!  If you don''t mind, and you do have a crash log, it still might be 
helpful to have it.  It might help me work around what every might be going 
wrong with the upgrade and auto-detect and fix the issue.
Thanks!

Original comment by spath...@gmail.com on 24 Aug 2014 at 8:38

[GoogleCodeExporter]

I guess not.

Original comment by spath...@gmail.com on 26 Aug 2014 at 9:05

[GoogleCodeExporter]

It would have been nice to address this potential crash before 1.7.1 by adding 
a check for whatever is wrong and at least displaying a warning dialog about 
needing to reinstall rather than crashing.
Without further details, I cannot do so.
I guess I'll just close this.

Original comment by spath...@gmail.com on 4 Sep 2014 at 9:37

[GoogleCodeExporter]

Original comment by spath...@gmail.com on 4 Sep 2014 at 9:37

• Changed state: NotReproducible

[GoogleCodeExporter]

I thought I sent you the crash report

Original comment by solark...@gmail.com on 4 Sep 2014 at 9:40

[GoogleCodeExporter]

If you sent it by email, I never got it.  Just checked spam folder to make sure.
Ideally, it should be attached here.  I'll reopen, if you want to try again.
Thanks.

Original comment by spath...@gmail.com on 4 Sep 2014 at 9:55

• Changed state: Accepted

[GoogleCodeExporter]

Here is a link to a doc with one of the crash reports.
I hope it helps you.
Best
James

https://docs.google.com/document/d/10C8VxUtV8J0oxoZqJ_pbxWvjHPTcXkYpHBQoY8HXgzM/
edit?usp=docslist_api

Original comment by solark...@gmail.com on 5 Sep 2014 at 1:41

[GoogleCodeExporter]

Thanks, but that's not a crash report for Frotz; it appears to be a log of 
cellular stats, which I notice on my phone looks like one of the files 
beginning with "awdd-" n the Diagnostics & User Data section.
The log file name of a Frotz crash begins with "Frotz" and then the date.
It's possible the file no longer exists on your device since it's been a while 
since the crashes occurred. 

Original comment by spath...@gmail.com on 5 Sep 2014 at 3:46

[GoogleCodeExporter]

Original comment by spath...@gmail.com on 9 Sep 2014 at 4:22

• Changed state: NotReproducible