7
votes

I'm trying to setup Parse crash reporting on iOS, using this guide, but unfortunatly, even after several crashes, there is nothing on my dashboard.

Here is my code (i'm using sdk 1.6.3) :

     - (void)crash {
        [NSException raise:NSGenericException format:@"Everything is ok. This is just a test crash."];
     }

     ...

     [ParseCrashReporting enable];
     [Parse setApplicationId:@"********"
          clientKey:@"********"];
     [self performSelector:@selector(crash) withObject:nil afterDelay:10.0];

I followed the troubleshooting guide:

  • Make sure you've enabled Crash Reporting in your App Delegate before you initialize Parse. DONE
  • If you're testing, make sure Xcode isn't catching the crash with the debugger. DONE
  • Build, run, stop the app, and then run it from the home screen. Crashes are sent on the next run of the app. Make sure the app isn't crashing again before it has a chance to send the crash information. If you're testing, you can ensure this by adding a delay. DONE
  • Crashes may take up to a minute to show up on the dashboard.DONE
  • Make sure you don't have any other crash reporting solutions linked to your application, as they might interfere with each other. DONE, (disable Flurry)

I tried on both simulator and device, as recommanded here.

Finally, i've this message in my console:

+[PFAnalytics trackEventually:params:]: unrecognized selector sent to class 0x10f08ac20

Any help is highly appreciated.

4
It doesnt work for me either- v1.6.3 the same error.vatti
I'm having the same problem. Tried using crash reporting in different apps, won't work.Peter Carnesciali
I'm having this problem in parse 1.9.0, anyone as well?Markus
Yes me too, I am having this problem in 1.9.0.Bocaxica
Still having this problem in 1.9.1.Tulleb

4 Answers

2
votes

Parse must have a bug in v1.6.3 because I have downloaded v1.6.0 and it works all fine. You can download it here:

https://parse.com/downloads/ios/parse-library/1.6.0

And this is the order for enabling:

[ParseCrashReporting enable];
[Parse setApplicationId:kParse_AppID clientKey:kParse_ClientKey];
1
votes

This probably doesn't count as any answer but I don't have enough rep to comment.

Have you tried enabling the crash report AFTER setting up parse with your keys? I know this was an issue for me when I was trying to enable the local datastore.

I know it goes against the guide but weirder things have happened when I use Parse...

1
votes

Parse 1.7.3 is also busted... upgrade to 1.7.4!! !

EDIT: DONT UPDATE TO 1.7.5 -- that seems to be busted too !!

0
votes

Latest version Parse SDK 1.6.4 fixes this problem! https://www.parse.com/docs/downloads