Our app uses AVSpeechSynthesizer to speak short pieces of text. After the release of iOS 11 we started to see crash reports on Crashlytics in the Apple private class, AXSpeechManager:
Crashed: com.apple.main-thread
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000010
libAXSpeechManager.dylib__61-[AXSpeechManager speechSynthesizer:didStartSpeakingRequest:]_block_invoke + 48
While debugging, I can see that this method is called when AVSpeechSynthesizer is speaking text. But I cannot reproduce this crash on device or in simulator.
Does anyone has the same issue or has clues what can cause it? Our app allows users to edit text which will be synthesized. Maybe, some users enter text that causes AXSpeechManager to crash?
Related
I am getting crash on iOS13 devices with a following crash log
Crashed: BSXPCCnx:com.apple.frontboard.systemappservices (BSCnx:client:com.apple.frontboard.workspace-service)
EXC_BAD_ACCESS 0x0000000104a1c458
App has Firebase, Facebook and Realm SDK which uses NSClassFromString. 96% crashes have occurred when app is in the background state.
We used NSFileProtectionComplete for data protection
One solution suggested on Apple Forum is, if NSFileProtectionComplete in entitlements, use NSFileProtectionCompleteUntilFirstUserAuthentication, then locking specific directories with NSFileProtectionComplete. But not sure this solution will work or not as not able to reproduce the crash. Any help will be really appreciated
With iOS 13.2 beta 3, the crash is not reproducible with above-mentioned step. Looks like the issue was from Apple and they have taken care in 13.2 release
There are many crashes reported for WebKitLegacy on Crashlytics and I have been using webview in my application. There is no way to figure out why these crashes occur. I have set the delegate and webview to nil in viewwilldisappear method. But still it is crashing. Can please someone help me in this?
[
This error might be misleading. Are you using NSAttributedString to load HTML or to display "web link" like button? If so you might be calling the HTML importer from a background thread. See details here:
Unable to reproduce WebKitLegacy -[_WebSafeForwarder forwardInvocation:] crash
As you can tell from the title, I am in a sticky situation where my App is crashing after performing a specific test. The test is as follows:
install App on iPhone 7
transfer iCloud profile to iPhone X
launch App (app will show splash screen and fail)
I was able to recuperate the .crash data from the iPhoneX however the data isnt very useful as the calls being made are all in hex. I am aware you can try to analyze the data through atos as well as other tools from this help link however it seems you always need the dSYM for most of the cases. I have the original .app and .ipa that was used to publish the app however there are no .dSYM files on the build machine. (I believe by default Apple has it set to build DWARF without dSYM)
Is there any way I can put the data from my .crash file to good use? The file is completely unsymbolicated.
(As a side note, a way to get out of the App crashing at launch after doing the iCloud transfer is to uninstall and reinstall the app from the App store. Not fun for an end user)
Snippet of the crash:
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Triggered by Thread: 0
Application Specific Information:
abort() called
Filtered syslog:
None found
Thread 0 name: tid_303 Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x0000000183f202e8 __pthread_kill + 8
1 libsystem_pthread.dylib 0x0000000184039748 pthread_kill$VARIANT$armv81 + 360
2 libsystem_c.dylib 0x0000000183e8efbc abort + 140
3 MyApp 0x0000000105ad4de8 0x104be8000 + 15650280
Is there any way I can put the data from my .crash file to good use without DSYM ?
No, it is impossible.
DSYM file stores all the debug symbols, with it we can find the corresponding function name via the memory address(in crash file) which leads to crash.
I have an app which is written in swift and uses AFNetwork and some other helpers written in Obj c. On my clients device (iPhone 6+) he is getting an SIGTRAP error, I have tried to recreate the issue on the testing devices that we have and on all the simulators but could not recreate it.
Below is the stack trace, it crashed twice:
http://paste.ubuntu.com/12077304/
When I symbolicate the crash report it is pointing to:
-[Instagram getOwnBaseUrl] (in DiaryApp) (Instagram.m:118)
And on the second instance it point to:
[UIAlertView(AFNetworking) showAlertViewForTaskWithErrorOnCompletion:delegate:cancelButtonTitle:otherButtonTitles:]_block_invoke (in DiaryApp) (UIAlertView+AFNetworking.m:72)
Crash Log : http://paste.ubuntu.com/12077328/
I am not able to pin point the exact cause for the crash. Any help in this regard will be highly appreciated.
Thanks.
SIGTRAP is not the error it is the exception. It doesn't show the origin of the crash. This exceptions throw into Main thread on Main/Next Runloop, so the stacktrace of the main thread does not show the origin of it.
It happen like NSArray indexOutOfBounds or library or anything else
reference link
signal Types
I have built an App in Swift but with Cordova which is Obj C. I also use crashlytics. I'm seeing a crash in about 10% of users, previously I experienced it a lot myself when using the debugger but since iOS 8.3 I don't, but that doesn't seem to have reduced the problem in the wild.
The crash is EXC_BAD_ACCESS KERN_INVALID_ADDRESS in CA::release_objects(X::List<void const*>*) + 32, called when the autorelease pool is drained. The crash is always in the WebThread.
I can't seem to reproduce locally with Zombies profiling, so it is difficult to narrow down any further, but I can't see what would be causing this in my code. I do use Core Animation but only in swift, and this was happening before I added the CA code. I use UIView animations, but again it is all in Swift with Storyboards and I can't think where anything would be going wrong. Any suggestions?