I have an OSX app that is constantly crashing on one device.
I have setup the project build setting to never strip symbols (debug or release):
When I build the app, I copy both it and the .DSYM files to a local folder. I then copy the app to the testing computer, where I launch it. After it crashes, I copy the generated .crash file (found via the Console app), to my local folder which also contains the app and .DSYM file.
In XCode, I switch to the Organizer window, choose import and select my .crash file.
Nothing happens. My understanding is that this should symbolicate my crash report, so that I can understand it better.
Any suggestions as to that i'm doing wrong? (Or if I don't have a proper understanding of how to symbolicate a crash log)?
I may have found the answer:
How do I symbolicate a crash report of a Mac OS X app that a user emailed to me?
That basically, XCode does not support symbolicating osx crash reports.
Related
UPDATE: This was fixed by resetting the phone's settings. General -> Reset -> "Reset all settings".
We are having on issue on iPhones 6 and 6+ when launching our IBM MobileFirst-based app.
When calabash instrumentation is linked and I manually launch the app, the splash screen will come up and the app will quit almost instantly.
Double tapping home shows me the app running in the background, but Xcode does not recognize it as a running process. After force-closing the app and re-launching, it will usually do the same thing, but sometimes it comes up.
I've noticed our automation is sometimes stuck in an infinite loop of launching and crashing. This only happens on the instrumented app.
The crash log throws EXC_BAD_ACCESS. I found a thread on the google group from a few years back that talks about linker flags, but I don't have any of the weaker flags mentioned there.
Steps to reproduce:
*App must be instrumented with the calabash automation framework (calabash-ios setup must have been executed in same directory as xcodeproj file.)
Build application and deploy native iOS project to XCode via eclipse.
Build the -cal target with the "Run" configuration.
Kill the debugger/application.
Manually launch the app on the device. The app will successfully launch maybe 15%-20% of the time, otherwise it will just quit.
Using calabash-cucumber version 0.14.3.
Linker flags:
$(inherited)
-force_load
"$(SRCROOT)/calabash.framework/calabash"
-lstdc++
It appears $(inherited) contains -ObjC for Debug.
Xcode installed at: /Applications/Xcode.app/Contents/Developer
Xcode version: 6.1.1
Xcode build: 6A2008a
The user is unresponsive, the fix was:
Actually I just found the fix to this. What I had to do is reset the
phone's settings in Settings -> General -> Reset -> "Reset All
Settings" (the first option). Have not seen the behavior since.
I had exact same problem, tried so many different ways and finally found how to fix it - I changed project directory, pulled from Git, then bundle install, pod install and build the app with calabash target as usual
Xcode 7.3.1, calabash-cucumber (0.19.1)
OS X 10.9.4
X-Code 5.1.1
I don't have Mac Developer Program account.
I created app for OS X, builded unsigned .app. It runs perfectly and works on my Mac. When I copy application to another Mac with the same version of OS X, try to run but nothing leads. Application icon starts appear in Dock and immediately disappears without any message. Running in the console gives an error "LSOpenURLsWithRole () failed with error -10810", unfortunately -10,810 is an unknown error.
I tried the same thing with a empty application "HelloWorld", it did not run too. Install and run applications from unknown developers in security setting is turned on.
I tried build LASlider example-project (https://github.com/Doshipak/LADSlider), that I use in my project. When I run it on another mac, app crashes like HelloWorld & my project..
Does someone has similar problems?
What had happened: Safari download invalid *.app from Dropbox with empty app body, same thing happens if you try to transfer *.app with TeamViewer. But result file looks normal.
Decision: always pack *.app in archive.
I am developing an iOS application and thanks to Xcode's "output log" I've been able to fix lots of bugs and such.
When I run my iOS application without Xcode, sometimes it crashes. However, it is hard to tell why did it crash since my device was not connected to Xcode. So I was wondering, when I run my iOS application, is there an output log like Xcode's stored somewhere within the iOS device I can retrieve? Or do I definitely need Xcode? Or perhaps there are other ways?
When you connect your device to your computer, open up the Organizer in XCode. There will be a device log tab that you can select to view device & crash logs.
Go in the organizer then on devices. You'll get logs in there.
If you are jailbroken you can use the syslog in /var/log/. I find it useful.
edit: You need to download syslogd to /var/log/syslog package on cydia also.
When I use the iOS simulator and the app crashes, I can't find the crash logs. I've been looking all over the internets and can't figure out how to enable them. I know I can just run on an actual device and get the crash logs that way, but the bug I'm trying to fix right now tends to cause the program to be hung in the debugger. Then there's no qlaunchsuccess packet sending and it's a huge pain, especially when I have to run the program over and over. The only advice I've been able to find says the use CrashReporterPrefs, but a search of my hard drive reveals nothing named something even close to this. I've also dug into the package contents of XCode and the files of the iOS simulator. The iOS simulator has a crash logs folder, but it is empty. Anyone know how to get this working? Thanks.
Run your App with Xcode to install the App to iOS Simulator
Launch your App on Simulator without Xcode
reproduce steps for crash
the Crash log should show up under this directory
~/Library/Logs/DiagnosticReports/
It appears if you aren't running Xcode (mine is 4.5.2) but just the simulator (mine is 6.0) that when an app crashes it does save a crash report. To view it bring up the Application/Utilities/Console and
(1) make sure it shows the log list (see top left of console to make sure not hidden)
(2) under "DIAGNOSTIC AND USAGE INFORMATION" there is a "User Diagnostic Reports" that if you open up should have your crash reports
(3) the area on the right of the console has the log
A Crash log is just an output of what the debugger already gives you. When you are running in the simulator attached to the debugger, and you hit the crash, you can view the back trace information in the debug navigator (default key binding is cmd+5)
I am building an app for iOS via commandline but I am having problems debugging it. Had I built using XCode, it would have let me "build and debug" on device without problems. But now, I don't know how to launch it on device using gdb and step through it. If I try to "add a custom target/executable" to a blank XCode project and then launch it, XCode complains about not finding the executable. Same thing happens if I install the app on device manually and try to attach to it using gdb within XCode. Any pointers on how to go about debugging this app? Changing the build process to use XCode is not an option.
This site gives a nice tutorial on how to manually set up a remote debugging session on an iOS device. The process boils down to creating a remote debugging server on the device and attaching to it with a local GDB instance.