Lastly I realize this issue using my real device in Xcode
If the app that I'm developing crashes, the crash log is not printed in Xcode but, if I run the same project in simulator and replicate the same crash the log is successfully printed.
If the app crashes using a real device this is printed:
After a crash it prints a single line:
libc++abi.dylib: terminating with uncaught exception of type NSException
Also I receive this log:
If the app crashes using a real device this is printed:
warning: could not load any Objective-C class information from the dyld shared cache. This will significantly reduce the quality of type information available.
I'm using:
Xcode 7.3.1 with iOS 10 developers disk image see reference.
Real device: iOS 10.0.2
Is there a way to solve this issue and see the crash information again using a real device in Xcode?
Thanks in advance
I've experienced same issue, and resolved it by removing "OS_ACTIVITY_MODE" - disable from scheme environment variables.
I was wondering if anyone could tell me what Xcode is actually doing when it says: "Processing Symbol Files" after plugging in your device?
It downloads the (debug) symbols from the device, so it becomes possible to debug on devices with that specific iOS version and also to symbolicate crash reports that happened on that iOS version.
Since symbols are CPU specific, the above only works if you have imported the symbols not only for a specific iOS device but also for a specific CPU type. The currently CPU types needed are armv7 (e.g. iPhone 4, iPhone 4s), armv7s (e.g. iPhone 5) and arm64 (e.g. iPhone 5s).
So if you want to symbolicate a crash report that happened on an iPhone 5 with armv7s and only have the symbols for armv7 for that specific iOS version, Xcode won't be able to (fully) symbolicate the crash report.
In Xcode Version 6.1.1 (6A2008a), after "Processing Symbol Files", a folder containing symbols associated with the device (including iOS version and CPU type) was created in ~/Library/Developer/Xcode/iOS DeviceSupport/ like this:
xCode just copy all crashes logs. If you want to speed-up: delete number of crash reports after you analyze it, directly in this window.
Devices -> View Device Logs -> All Logs
In my case symbolicating was take forever. I force restart my phone with both of on/off and home button. Now quickly finished symbolicating and I am starting run my app via xcode.
I know that this is not a technical solution but I had my iphone connected with the computer by cable and disconnecting the device from the computer and connecting it again (by cable again) worked for me as I could not solved it with the solutions that are provided before.
It compares crash logs retrieved from the device to archived (symbolized to be correct) version of your applications to try to retrieved where on your code the crash occurred.
Look at xcode symbol file location for details
Annoying error. I solved it by plugging the cable directly into the iPad. For some reason the process would never finish if I had the iPad in Apple's pass-through stand.
Add SDK version correspond to your iPhone iOS, eg: iOS 10.3
path:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport
It's downloading. When it's finished, it's OK. As shown in the figure:
Does anyone know why the organizer will not find my new crash reports for one iOS device but it does for my other devices?
Let me explain: I was demoing an app today on both my iPad 3 and iPhone 5. The app is still in beta so I experienced crashes on both devices. When I returned home later that day, the new crashes from the iPhone 5 appeared right away in the Organizer window. However, the iPad 3 did not have its new crash logs appear. The only logs that came up (even after waiting several minutes and restarting the device) were from a month ago. I am running iOS 6.01 on the iPad 3 and iOS 6.1 beta 3 on the iPhone 5. Does anyone know why this might be?
Look at the console for the device to see if there is any extra information about why this might be happening. I've seen this occur when the device is full of crash reports, if this is the case you will get info about this in the console for the device.
One of my apps recently were rejected due to not running on iPad in compatibility mode. However, I fixed the problem and they load fine in Compatibility mode on iOS6 on my iPad simulator through xcode. So I reuploaded my app and about 7 hours later it already went into review and got rejected for the same reason, they said that the app crashed on iPad.
So, how do I read specifically the .crash file returned by apple?
I've upgraded my iOS on iPhone 3G to 4.1 and now I run my app on the device.
Firstly, I couldn't install it becouse Xcode was saying I don't have certification etc. (I have jailbroken iPhone). Finally, I succeeded and installed it.
But know something strange happens....
After I had installed my app on the device I run it.
Then, "cocos2d" image appears on the screen and just a second later device switch off! It simply reboots.
What's more - when the device launchs again and I run my app - it works!
I have no idea what's going on. This app works fine on 3.1.3 iOS (even with the same Xcode - 3.2.5)
What should I do?
Do you think the problem is caused by Xcode or iPhone itself?
Maybe reinstalling Xcode may help?
It could be one of two problems.
It could be a problem with your device. Maybe something got sort of wonky with your jailbreak.
Secondly, it could be a problem with your app. Maybe it's crashing. Have you checked your crash logs?