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.
Related
We are developing a Watch OS companion application for our iOS app. We currently get symbolicated crash reports for our iOS app on App Store Connect. We are trying to get the same for the Watch Application.
We are producing some forced crashes on a build we uploaded to TestFlight but crash logs are not getting there as iOS crash logs. Is there anything else that needs to be done differently from iOS to get them?
Do you know about any known issues on it?
BTW, we see the crash logs getting to the iPhone on the iPhone itself. They're just not uploaded. We are also able to get the logs on Xcode Organizer.
A simple swift app I built is returning two dyld errors in the debugger pain in Xcode 8.3.2. The apps worked on my iPhone (7 running iOS 10.3.2) and iPad (4 running iOS 10.3.1) for a few weeks but then would crash immediately on launch without even loading the first page. I updated my provisioning profile (which had expired) and attempted to reload the app on my iPhone and iPad. Both devices show just white screens when connected to my Mac and attempting to launch the app in Xcode. Any idea what might be causing this error? dyld error screenshot 1
dyld error screenshot 2
Using the product->clean in Xcode fixed the problem, thank you rudydydy.
This appears to have been a compiler induced error.
I am encountering a strange behaviour, my app runs smoothly on simulator but crashes on device.
Also when i try to detect leaks using instruments it just crashes on both simulator and device.
I am totally stuck as i am not even able to generate any error message on console, also NSZombieEnabled is on in the settings.
I can see two possible reasons for the behavior you describe:
device is short on memory; (but you would see some processing in this case)
your app uses a newer SDK than what you have installed on your device (like using the SDK 5 twitter framework and then running your app on an SDK 4 device).
Specifically, in case 2, you would not see any log messages because the app would fail as soon as it tries to load the missing framework in memory.
In any case, inspect the device log in Xcode Organizer window to have more info about the crash. This is the only way you can understand what is happening.
the app I've installed on an iPhone 3G device periodically crashes. I'm wondering if it's the device or the code. the code works fine on the simulator.
I have other apps from the app store that do the same thing. e.g. the stackoverflow app - whenever I do a search the app crashes. I've even had the iPod app crash too.
I've restored the phone a few times and still the same thing. I'm getting ready to upload the app to the app store and was wondering if anyone had any tips to make sure that my code is not the problem. it's difficult to tell because there are no errors in the simulator or memory leaks in Instruments
thanks in advance.
You can be guaranteed that it is your code. Run it in the debugger on the device and see where it is crashing. If you are getting EXC_BAD_ACCESS use the following to help track it down
http://www.cocoadev.com/index.pl?NSZombieEnabled
It most certainly is your code that crashes.
Run in debug mode and watch the console (real debug mode, not only the debug target).
Also, you can (and should) grab the crash report from the organizer. You can also watch the device's console there.
Are you sure you are not running out of memory?
the easiest way to see if this is your problem is to implement didReceiveMemoryWarning method of your controllers and check if they are called.
In the simulator you can simulate a memory warning but I am not sure if even in simulator app will crash if memory is not released. (I believe not)
Also run your app with instruments, using allocations: Run > Run with performance tools > Allocations.
And use your app for a while and you will see. ;)
So my app uses MapKit, and many of the people who have downloaded my app are complaining that it crashes right after the map loads. I can assume that its crashing once the annotations are being displayed on the map. I have no history of crashes in my itunes connect crash logs (should i??), but they posted in a review that they're using iphone v1, and iOs 3.1.3. I have never been able to replicate this crash myself, and I think it may be because the lower version supported by the simulator is 3.2.
Does anyone know who I can debug in this situation?
Check multiple annotation at Same Lat log.