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
Related
After working just fine on both iPhone and iPad for a month, my Xcode 9 app has consistently started crashing causing me the following fatal problem: When I build & run it on an iPhone (simulator or device) Xcode completes loading the app and then crashes too fast for me to copy/paste the error from the debugger. When I run on iPad it works fine leading me to believe this is a result of something related to the split master/detail view.
If I use either an exception breakpoint or an "all C++ exceptions" it will stop at the AppDelegate class and crash if I hit play. If I use only an "all Objective-C exceptions" it will crash as before.
In the debug view hierarchy I get the following errors as well:
Error: Unable to capture view hierarchy.
Details: Log Title: Data source expression execution failure.
Log Details: error evaluating expression “(id)
[[(Class)objc_getClass("DBGTargetHub") sharedHub]
performRequestWithRequestInBase64:#"...
Log Method: -[DBGDataSourceConnectionLibViewDebugger
_executeLLDBExpression:forRequest:onPotentialThread:iteration:]
_block_invoke_2
Method: -[DBGViewDebugger updateDebugHierarchy]_block_invoke_2
I have tested other apps and this issue is unique to the app I am working on. Any ideas or debugging tips for how to proceed? I might just have to redo this whole project again if I can't even find the root cause of this! Appreciate any help.
Quick solution: Reset Simulator Device
I managed to resolve the above issue thanks to some serious digging. First, to resolve the instantaneous crash problem, I set a breakpoint at every line in the app delegate. That allowed me to narrow the error to a memory handling problem. From there I started running the code on one of each device available, and realized the crash only occurred on devices I had used earlier in development. Resetting those devices solved the problem.
The core issue here is that when you clean/rebuild your xcode program, it updates the app code on the device, but not necessarily the data model information. So when I changed my data model by including new data and renaming old data it was not properly updated.
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 used Bugly(a tool same as Crashlytics) to recored crashes in my app which had released.But sometimes there are some crashes in main.m as the report showed:
With these information I can't location problem in my code at all.I need to know which class and which method the problem occured so I can location this problem.
I wonder is there any way I can location problem more precise?And how do you deal with these crashes in your released app?
Wish you can share,thanks a lot.
Finally I find this is memory leak result.Use Xcode instrument check is a good way.
I have an app I'm developing where setting a breakpoint in Xcode while the app is running causes it to crash. At least I assume it is a crash. There is nothing in the console saying what happened. The app just terminates.
Note that the break point is not being hit, just the act of setting it causes this.
I've developed many apps and this is the first to act like this. Does anyone have any ideas what could be happening or how to figure this out? It is really slowing down my debugging.
I'm assuming you're using Xcode 4.x. Try going into your scheme's settings and switch to a different debugger (GDB if you have LLDB currently set, or vice versa).
If that doesn't work, we need more info:
which version of Xcode and iOS are you using?
does the problem occur in the Simulator or on your device, or both?
have you tried placing a breakpoint in different places in your code?
As far as I can tell, it's a debugger issue. So your app does not actually crash, it's the debug session that crashes which causes the app to terminate. You can observe a similar effect when you hit Stop in Xcode or disconnect your device while an app is attached to the debugger in Xcode.
Might be an issue with mismatching Xcode and iOS versions. Please provide more info about your environment to help diagnose the problem.
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.