When I run my UITests they sometimes fail with a weird cause upload-symbols crashed in <external symbol>. The only work around I found is to restart Xcode, which helps most of the times, but I'm already tired of doing this.
The UITests scheme is setup correctly and I am able debug the main target during the execution of UITests, so I suppose dsym info is available. The main app doesn't crash and doesn't catch any exception breakpoints when test fails.
The failure happens at random moments of time and during execution of random tests. I haven't seen it happening on CI, which launches UITests from terminal via fastlane.
I appreciate any advice.
Xcode 10.3, I'm not sure this was happening on 10.2
MacOS 10.14.6
I'm not sure, but I faced with same error:
crashed in <external symbol>
I run ui-tests at CI and cause of my error:
Other pipeline delete and reset my current running simulator.
Also, try find out how to fix this trouble.
I use fastlane-plugin-test_center
This is definitely an Xcode bug. I realized, that this crash happens way less likely if I run all tests rather than a specific testcase/test. So I end up disabling all of the tests in the target while developing, except the one I work on and just run them with CMD+U.
Related
I'm seeing some truly bizarre behaviour from lldb in one of my projects. When I stop execution at a breakpoint and enter anything at all in the debugging console, there is no response:
I'm running a debug build here. The issue does not occur in other projects, where I can debug without issue.
This is a real head-scratcher. Has anybody run into this before?
I solved the issue, but in an unsatisfying manner; by getting a fresh clone from git.
I suppose one of the files in the standard Xcode .gitignore got weird and caused this behaviour.
In Xcode 6.2 I created a test target called CommonTests:
and wrote some tests in it that are all passing on my machine:
I marked the scheme as shared so other developers could easily run them:
Another developer tried to run them and got an error that I don't understand yet, but in the investigation, we discovered his Xcode is seeing the test target quite differently than mine:
Any ideas what's going on? Anything we can delete for Xcode to refresh the known tests from the code and shared scheme?
Most of what I was seeing, like the list of tests, is gathered by Xcode after running the tests and because the tests were crashing, it was never gathered. It was an irrelevant side effect to the actual problem.
The actual problem is that the tests were targeting 10.10 and the other developers were running 10.9.
Today our Calabash-iOS tests stopped working, after XCode updated to 6.1. Yesterday all was fine, today (with no code changes having occurred) it does not work.
When trying to call touch inside our step definitions, nothing happens, until eventually a timeout occurs and the following error is displayed:
uia action failed because: Timed out running command uia.tapOffset('{:x 160.5, :y 295}')
This worked fine yesterday (before XCode updated itself). The problem affects both machines we have that updated but does not affect another machine that has not updated.
We are using the latest calabash gem (0.11.1), but I've tried downgrading to 0.10.1 with no effect.
Incidentally, I tried downloading some sample apps from Apple (https://developer.apple.com/devcenter/download.action?path=/wwdc_2014/wwdc_2014_sample_code/advanceduserinterfacesusingcollectionview.zip and https://developer.apple.com/library/ios/samplecode/UICatalog/UICatalogCreatingandCustomizingUIKitControlsObj-CandSwift.zip) and then following the installation instructions at https://github.com/calabash/calabash-ios . The simulator could be started with the -cal Target with the expected console output, but trying to run cucumber failed as it would keep attempting to launch the app in a continuous loop.
Any ideas or suggestions would be welcome. If necessary I will uninstall XCode and re-install the previous version, but I'd like to get this resolved in a more satisfactory manner.
This now works, as of calabash-ios 0.11.4 with Xamarin Test Cloud Agent Component 11.4.
I have a new machine that is a clean setup of Ruby, Cucumber, and Calabash-IOS.
When I try to run cucumber from Terminal I get an error popup from instruments that says
"Unable to interpret path (null)" and the simulator never launches
I tried changing the APP_BUNDLE_PATH and I tried commenting out the APP_BUNDLE_PATH, neither worked.
This is a compiled .app file that was built using Xamarin Studio. I am assuming that instruments is having some problem with this .app file for some reason when it is trying to launch it? This same setup works fine on other machines so it must be an environmental
problem.
Is there a way to get a better output log from cucumber or calabash (or instruments) so I can figure what exactly is throwing this error? Or does anyone have any ideas of what I can try to get calabash to launch my .app correctly in the simulator?
For anyone who might stumble over this in the future.
In my case the issue was caused by an invalid .app package. I still don't know what was wrong with the specific package itself but something inside the .app must have been invalid causing the error. I recompiled my application and replaced the .app file that was being loaded but calabash and the problem went away.
a more informative error message would have been nice (something like, corrupt .app package detected) but oh well.
Hope it helps someone else in the future.
The error:
Error spawning child process: Permission denied
pops up in the console about one in every five or ten times that I try to run my project in the Xcode simulator. When this happens the project does not run.
Rerunning the project (Cmd-R again) usually works.
Can't find any mention of the error on Google, anyone experiencing this?
Edit 2014-07-04, getting this error too.
Running XCode 5.1
Cheers,
Paul
I had the same problem and after some Product -> Clean the message disappeared. So you should try that way!
I've had to do a clean build of the project and restart both the Xcode 5.1 and the iOS Simulator to solve the problem.
I had the same error. I removed a few lines of commented code, and cleaned the build, before compiling it again. Sounds crazy, but it worked.
Are you having any LLDB errors along with the "Error spawning child process" one?
I'd same issue with xcode5.1.1. Resolved by following steps.
Clean build
Change simulator selection to iPhone Retina 4 and Run , then back
to iPhone 3.5 screen, it works.