Recently, our app collected many of these crashes through the fabric (most of them crashed on 11.2
Crashed: MRAVConcreteRoutingDiscoverySession
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x00000004d407bec8
Related
A react-native app I inherited throws this error Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'rootViewController is not of type HomeIndicatorView as expected.'
The app on load shows the splash screen and gets stuck on the screen below. At the moment, I don't know where to look as most of the solutions online doesn't lead anywhere.
PS. I'm using MacBook M1 pro, incase this is an issue with M1's.
I was trying to compile a sample app with Salesforce React Native SDK 4.3 and Xcode 8. The app would build successfully, but when loading on the simulator, it would crash at the splash screen and at the following line of code:
int retVal = UIApplicationMain(argc, argv, #"SFApplication", #"AppDelegate");
I got the following errors in the output:
ibc++abi.dylib: terminating with uncaught exception of type NSException
and further up
Terminating app due to uncaught exception 'com.salesforce.security.keychainException', reason: 'writeToKeychain: Error adding keychain item: Unknown status code (-34018).'
It seems that enabling Keychain Sharing under "Capabilities" will fix the problem. I believe this issue should be fixed with SDK 5.
There is a bug which only happens to my app on OS X 10.6 and OS X 10.7: the app crashes on closing.
Explaining it better: when the user closes the app window (closing the app by consequence) the user see a crash dialog, which means that the app crashed while closing.
I've managed to get the help of an OS X 10.7 user to use a Debug version of the app, imagining it would produce a crash log easier to understand, however nothing changed.
Process: MyApp [838]
Path: /Applications/MyApp.app/Contents/MacOS/MyApp
Identifier: MyApp
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: MyApp [650]
Date/Time: 2016-07-20 17:38:24.043 0200
OS Version: Mac OS X 10.7.5 (11G63)
Report Version: 9
Crashed Thread: Unknown
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00007fff5fc01028
Backtrace not available
Unknown thread crashed with X86 Thread State (64-bit):
rax: 0x0000000000000055 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x0000000000000000
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x00007fff5fc01028 rfl: 0x0000000000010203 cr2: 0x00007fff5fc01028
Logical CPU: 0
Binary images description not available
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 316
thread_create: 0
thread_set_state: 0
From Report Version and beyond, everything is always precisely the same, except for the task_for_pid.
I know it doesn't affect the program use since it only happens after the program closure, however it surely must be a pain seeing a crash report every time you close an app.
Remembering that this bug doesn't happen with OS X 10.8 or superior versions, and that I'm using the 10.11 SDK.
Finally I solved the problem. Despite OS X saying the crash belonged to my app, it wasn't exactly that. In my applicationWillTerminate: function I was running a binary throw NSTask, however that binary was compiled to be 10.9+ compatible, and that was causing the crash.
Rebuilding the binary with OS X 10.6 as the target version fixed the crash. Partially like #Willeke suggested, I installed Snow Leopard on my Mac (dual boot) in order to test my app in it, so now I will test it in Snow Leopard and El Capitan; the oldest and newest (while Sierra don't get a stable release).
I don't know why that bug didn't happened in OS X 10.8 as well; probably Apple has changed the way the system should behave to that kind of problem.
Im experiencing something strange while updating my app in the Appstore. Version 1.4 worked fine for every device. However Version 2.0 crashes on some devices when updated. The loading screen wouldnt even show when starting up and the app would crash within a second. Removing and reinstalling the application from the app store solves this problem. Again this only happens on some devices (iPod, iPhone 4, iPhone 4s, iPad so far).
I manages to get my hands on a crashing device and check the Device logs. Also I think I found something but I cant really understand the error. It says:
Dyld Error Message:
Library not loaded: /System/Library/Frameworks/AdSupport.framework/AdSupport
Referenced from: /var/mobile/Applications/(ID)/AppName.app/AppName
Reason: image not found
Dyld Version: 199.6
I added AdSupport.framework because I implemented Facebook in my App in version 2.0 and the file is in my project in the folder 'Frameworks'.
Does somebody know how to fix this?
Here is the full crash Report if useful.
Incident Identifier: ID
CrashReporter Key: crash key
Hardware Model: iPod4,1
Process: AppName [35491]
Path: /var/mobile/Applications/id/AppName.app/AppName
Identifier: AppName
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2013-03-05 23:23:35.041 +0100
OS Version: iPhone OS 5.1.1 (9B206)
Report Version: 104
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x00000001, 0xe7ffdefe
Crashed Thread: 0
Dyld Error Message:
Library not loaded: /System/Library/Frameworks/AdSupport.framework/AdSupport
Referenced from: /var/mobile/Applications/(id)/AppName.app/AppName
Reason: image not found
Dyld Version: 199.6
Binary Images:
0x7a000 - 0x106fff +AppName armv7 <0c108dce50ee3e65970e2538a3e319f8> /var/mobile/Applications/(id)/AppName.app/AppName
0x2fe79000 - 0x2fe9afff dyld armv7 <77eddfd654df393ba9c95ff01715fd08> /usr/lib/dyld
0x3075a000 - 0x307d9fff libsqlite3.dylib armv7 <bf01f5ed47b033d8bde30d735ff44416> /usr/lib/libsqlite3.dylib
0x3113c000 - 0x311a0fff MessageUI armv7 <da7af4f9494b35558bf7892dfdb36ee3> /System/Library/Frameworks/MessageUI.framework/MessageUI
This iPod has iOS 5.1 but I also received report on iOS 6.1
Because AdSupport.framework, is ONLY available on iOS 6. So Dyld cannot find something who doesn't exist on past IOS. Even if you are adding framework into your project, you don't actually include the binary, only the reference.
If it's not crashing when you are reinstalling your app, it's because maybe it doesn't use the adSupport functionality at that time. But i'm not sure of this theory because i haven't made your code ;)
Here the apple available framework link, hope it will help you
http://developer.apple.com/library/ios/#documentation/miscellaneous/conceptual/iphoneostechoverview/iPhoneOSFrameworks/iPhoneOSFrameworks.html
I use Mobile Payment Libraries for iOS PayPal intergration and when I lunch the demo example run on iOS 4.3 simulator only but when lunch on iOS 5 simulator I got this error.
SimpleDemo[3594:ef03] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSCFConstantString rangeOfString:options:range:locale:]: nil argument' </i>