I'm using crittercism to get the crash report from my iPad app. I want to know if the app crashed last time when it was loaded, but it seems that the CrittercismDelegate which contains
function crittercismDidCrashOnLastLoad is not working.
Any advice? Has someone faced this problem before?
Look like this was fixed in v3.2.6 of the library:
https://www.crittercism.com/developers/downloads
There was a bug where the delegate wasn't getting called until the load after a crash was sent to our server instead of after a crash was detected in the app. We pushed out a fix for this bug in v3.2.6. Make sure you are using the following to set the delegate:
[[Crittercism sharedInstance] setDelegate: whateverObjectYouWant]
Indeed using v_3_2_6 sdk the bug for setting the delegate is resolved.
Related
Many crashes happened below the iOS9.3 (which means devices with iOS10 are OK)..
The crash logs seem to show that it's not a problem about API that can only be used below iOS 9.3 .
But I have no idea about the crash logs. ( I'm sorry ...for I just start to study iOS development for only 2 month )
Could you please help me analyze the crash logs ?
Really Thanks !
crash log 1
crash log 2
AXE_BAD_ACCESS - this is problem with memory. One of function tried to use variable which already released. I think you need to check use your TableView and cells for this table.
Also to find problem with memory you can try to use zombies
Used to have the similar strange crashes in my app. And only in production, when testing from TestFlight. Building on device with ios 9 caused no problems.
Maybe it sounds strange, but try to convert all images you use in app to images with included sRGB color profile. For me it helped.
I have a weird crash reported by Crashlytics:
[SFSafariViewController setIsInitLanguageConfigSet:]: unrecognized
selector sent to instance 0x100d75fb0
The crash happens in a class that doesn't contain anything related to SFSafariViewController, It's just a simple page containing 3 options related to which language a user wants the app to be localized to.
Has anyone experienced such crash?
Apparently, it was Facebook SDK that was causing this issue.
Updating to the latest version fixed it.
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.
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];
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...
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 !!
Latest version Parse SDK 1.6.4 fixes this problem!
https://www.parse.com/docs/downloads
On my app, when I add the googleCast SDK, the app crash at launching, on this method [[DCIntrospect sharedIntrospector] start];. But when I don't have GoogleCast SDK, everything is working fine.
Here is the assertion log :
*** Assertion failure in -[GCKPB_PBFieldDescriptor initWithFieldDescription:rootClass:], /Volumes/BuildData/pulse-data/agents/wpye22.hot/recipes/415961027/base/googlemac/iPhone/Chromecast/SDKv2/Protos/../../../../ThirdParty/ProtocolBuffers/objectivec/Classes/PBDescriptor.m:409
This works fine if I run the project on an iPhone 5C, but crashing on the simulator (32-bit simulator).
Any idea on how to solve this crash, and still continue to use DCIntrospect ?
I had the same issue.
I was able to reproduce this issue, so I filed this bug.
Introspection triggers the +initialize method of the GCKPB_PBGeneratedMessage class.
This method apparently makes some bad assumptions about when +initialize will get triggered.
While waiting for a fix you can always use the workaround suggested here and mock GCKPB_PBGeneratedMessage's +initialize method.
I'm using crittercism to get the crash report from my ipad app.
What i need is to check if the app was crashed last time loaded at startup.
I'm using the CrittercismDelegate that contains crittercismDidCrashOnLastLoad on the appDelegate of my app but it seems does not work !!
any example/suggestions on this ?
this is Rob, one of the co-founders of Crittercism. That's a known bug that we're releasing a fix for early next week!
We will be adding some more info on our support page shortly:
https://www.crittercism.com/developers/feedback