I have integrated Flurry 4.3 SDK in my app, also uploaded the correct Desym file. I not getting the object and method call info for crashes in some cases, but i am getting them in other cases.
This is what i am getting in some cases.
17 MyApp 0x0009744f __mh_execute_header + 394319
I have added the following lines in app delegate.
[Flurry setCrashReportingEnabled:YES];
[Flurry startSession:kFlurryAppKey];
Please help me out in resolving this, as i am not getting the full readable stack trace.
Related
In an iOS project that uses Google Sign-In SDK (v5.0.2, added manually to the project, as well as GTM and Firebase), we have a crash that we could reproduce several times with a specific account on a specific device, when trying to sign in with a Google account.
The crash is:
** Assertion failure in +[UIAlertAction _actionWithTitle:descriptiveText:image:style:handler:shouldDismissHandler:], /BuildRoot/Library/Caches/com.apple.xbs/Sources/UIKitCore/UIKit-3901.4.5/UIAlertAction.m:42
The stack trace says the crash appears in
+[UIAlertAction actionWithTitle:style:handler:]
-[GIDEMMErrorHandler passcodeRequiredAlertWithCompletion:] + 556
-[GIDEMMErrorHandler handleErrorFromResponse:completion:]_block_invoke + 724
Poking with the debugger, it looks like UIAlertAction is passed a nil title, which causes an assertion failure.
The OS of the device is iOS 13.3.1.
I can't find an official way to report a bug in the Google Sign-In SDK, the Google issue tracker seems to be restricted to people with specific permissions, and they otherwise point to a forum that doesn't exist anymore, or to Stack Overflow...
The problem is that the resource bundle isn't being correctly linked in your project so the SDK gets a nil string for the action dialog which triggers the crash.
Until Google will gracefully fix it by providing a fallback string you can verify how you are linking the GoogleSignIn.bundle in your project
I am seeing the below error in iOS 13 when trying to setup an app with universal links. Has anyone seen this or know what it means?
I am seeing this error in the device console for the swcd process.
Error getting enterprise-managed associated domains data. If this device is not enterprise-managed, this is normal:
Error Domain=SWCErrorDomain Code=1701 "Failed to get associated domain data from ManagedConfiguration framework." UserInfo={NSDebugDescription=Failed to get associated domain data from ManagedConfiguration framework., Line=250, Function=<private>}
When I install the same app on an iOS 12 device it works perfectly fine. Any thoughts would be appreciated
It seems that upgrading to iOS 13.2.2 solves the issue.
There is no official confirmation about this, but is seems resolved on iOS 13.2.2.
There may be some different places that cause this problem. Note that the format of AASA file seems to be changed recently. Please refer to this.
If the delegate isn't called, and there are some Google Analysis or Firebase features in the app, then it may be caused by method swizzling. If that's the case, please refer to my answer here.
I'm using Fabric.io to monitor and collect crash data for a IOS app.
I'm receiving now a lot of crash reports for this error "Crashed: com.apple.root.default-qos" but when I check Fabric to analyze it I got the following report:
where the stack-trace of the crash is missing.
What should I do to receive the complete stack-trace?
App uses some libraries imported using CocoaPods.
I'm attaching here also a screenshot with linked libraries:
I have discovered that this report was sent because of missing "Privacy - Face ID Usage Description" (NSFaceIDUsageDescription) in Info.plist.
I have no idea why the report was not complete, but after adding this key my app has stopped crashing.
Parse version 1.6
Crash analytics are not working.
I am not able to see the crash logs in dashboard. Configured my app according to this:
https://parse.com/docs/ios_guide#crashreporting/iOS
I see the following message when I run the app on simulator:
Breakpad Uploader: unable to determine minidump file length
Any help is highly appreciated.
I suggest you to try using the device for testing the crash report feature, as by design the simulator doesn't work.
"Crash Reporting for iOS only works on a device and not in the simulator." - Björn Kaiser, from Facebook.
did you initialized crash reporting in app ? ;
// Enable Crash Reporting
[ParseCrashReporting enable];
// Setup Parse
[Parse setApplicationId:#"parseAppId" clientKey:#"parseClientKey"];
or if you are using Swift
// Enable Crash Reporting
ParseCrashReporting.enable();
// Setup Parse
Parse.setApplicationId("parseAppId", clientKey:"parseClientKey")
If not please do
You can always follow these step by step Tutorial on how to set it up
hope it helps.
I'm trying to get bugsense working in my iOS app but the app is crashing with EXC_BAD_ACCESS while initializing the BugSenseCrashController:
BugSenseCrashController *crash =
[BugSenseCrashController sharedInstanceWithBugSenseAPIKey:#"<Your BugSense API Key>"];
My key is correct and I've followed all the instructions listed here: http://www.bugsense.com/docs/ios
Not sure where to go from here.
EDIT
I've changed my code so I'm not using userDictionary (don't need it at the moment). Issue still persists.
EDIT2
It seems this is only happening when I run the code on the device (4.3.5) and not in the simulator (4.3).
Set NSZombieEnabled, MallocStackLogging, and guard malloc in the debugger. Then, when your App crashes, type this in the gdb console:
(gdb) info malloc-history 0x543216
Replace 0x543216 with the address of the object that caused the crash, and you will get a much more useful stack trace and it should help you pinpoint the exact line in your code that is causing the problem.
See this article for more detailed instructions.
Try adding following frameworks:
1. SystemConfiguration
2. libz.1.2.5