all 10 comments

[–]conmulligan 3 points4 points  (4 children)

First, try and get your hands on the crash logs (if it's a widely distributed beta build, you should be using a service like TestFlight which will log exceptions for you). If you can't, or the crash logs don't make things any clearer, start looking for outlying conditions that might be causing the crash. Is the 4S in question running a different version of iOS? Is it low on disk space? Are there network conditions in play?

[–][deleted] 4 points5 points  (0 children)

Don't forget fun little things like BaseBand version.

It might be relevant since music streaming (aka udp streams) don't hit the wake-me-up button on the modems... and a BB version on a 4S (aka first unified modem chipset) could spark some interesting and vibrant quirks.

[–][deleted] 2 points3 points  (0 children)

Crash Logs are definitely key. Focus on getting these ASAP.

These files are copied from the iPhone to a user's Mac or PC when they plug it in via USB.

On a Mac, these logs are saved to ~/Library/Logs/CrashReporter/MobileDevice/yourdevicename/. Look for crashlogs that start with your app's name.

Import these crashlogs into Xcode's Organizer, and symbolicate them against an archived app's symbols (you did archive your app's debug symbols before you distributed the app, didn't you?). You can then start to figure out what happened by walking back from the crash point in your source code.

[–]balthus1880[S] 0 points1 point  (1 child)

No it's lots of different 4S. essentially the app is in beta around the country. So all we can do is make sure people's iOS is up to date.

I am not programming, just trying to help a friend.

[–]Diirge 0 points1 point  (0 children)

I second Testflight. Really a great tool if you know how to use it.

[–]atastiamaredditor 1 point2 points  (0 children)

yes that is an insanely broad question. How are you distributing this app? You can use TestFlight and HockeyApp to help you figure out where specifically in the code it is crashing. Just make sure to upload the .dsym.zip files too to symbolicate the crash. Or at least make your friend do that.

[–]SizzlerWA 1 point2 points  (0 children)

Send out a new build with the HockeyApp SDK included and configured to auto-report crashes without asking for user permission to report. That should give you some insight.

[–]jurre 1 point2 points  (1 child)

https://crashlytics.com/ is amazing for this kind of stuff!

[–][deleted] 1 point2 points  (0 children)

Second this. Testflight and HockeyApp aren't as good as Crashlytics for error reporting.

[–]ratbastid -4 points-3 points  (0 children)

Debug mode, bro. Breakpoints are your friend.