I am trying to run Xcode UITesting on a physical device (iPod), but am getting the error :
Test Target UITests encountered an error (Early unexpected exit,
operation never finished bootstrapping-no restart will be attempted).
The specific line that is triggering the error is :
[[[XCUIApplication alloc] init] launch];
I have noticed that the UITesting app does not launch on the device, instead on the test target app is launching, which I assume is the issue. Any ideas on how to fix this?
I was able to fix this bug by altering the build settings, specifically bundle loader. I removed build/Debug-iphoneos/MY_APP.app/MY_APP from debug and build/Release-iphoneos/MY_APP.app/MY_APP. I then added a couple additional compile sources and was able to get the UITesting to function again.
Related
I have created some Bots to build, analyze and run unit tests, but I have not been able to make it work in a simulator. All integrations always finish with 12 errors, one for every simulated device.
Assertion: Test target MyAppTests encountered an error (The operation couldn’t be completed. (OSStatus error -1712.) If you believe this error represents a bug, please attach the log file at /Library/Developer/XcodeServer/Integrations/Integration-7d62a04eb43957f1d3098c8ffb64cc13/Session-2016-06-22_20:00:39-svEh7I.log)
This same error repeats itself 12 times. I believe it has something to do with the simulators because the tests only pass on the real devices.
Is there some trick that needs to be done for the simulators to work? The bot configuration for devices is to test with All iOS Devices and Simulatos.
Thanks in advance.
I have a set of XCUITests that run with our iOS app. They used to run fine on Xcode 7.2.1, but upgrading to 7.3 causes tests to fail in the "Set Up -> Wait for app to idle" phase with the following error:
UI Testing Failure - Failed to perform AX action for monitoring the animations of <XCUIApplicationProcess: 0x7f82450288c0 [appName here] (25670)>, error: Error -25204 performing AXAction 2043
This failure is seen on every single UI test, both on bots and when running locally.
Has anyone else seen this or have any workarounds?
In case anyone still has this issue - for me it was activating the Optimizely framework that caused this error. Disabling the framework when running XCUITest solved it for me.
Note to self: Don't have code that crashes your app on purpose while tests are trying to run. D:
Basically there was a call to terminate the app within the launch phase of the app for a certain scheme (in our case, the TEST scheme). Be thorough in checking what the app is doing when it launches for testing, because there might be errant behavior.
I start a new project from File -> New -> project
I add a button to ViewController.
I open UITest folder which created by xcode by default. Run the test code.
It fails:
2016-03-16 12:57:09.191 XCTRunner[3511:150419] Continuing to run tests in the background with task ID 1
t = 10.18s Assertion Failure: UI Testing Failure - Failed to background test runner.
/Users/Bernard/Desktop/ExampleTestApplication/ExampleTestApplicationUITests/test2.m:27: error: -[test2 testExample] : UI Testing Failure - Failed to background test runner.
2016-03-16 12:57:12.789 XCTRunner[3511:150419] *** Terminating app due to uncaught exception '_XCTestCaseInterruptionException', reason: 'Interrupting test'
Now I add a break point as follow:
Now test is successful! Anyone can explain the reason?
I was also facing same issues and none of the available solutions worked for me. Issue was not letting app to attach to the simulator itself.
I checked the log and saw that i did a mistake in code while locating the element. for Predicate instead of BEGINSWITH i wrote STARTSWITH and this was stopping the app to get attached.
So check your logs in the test report to get the issue.
I was getting this error happening when the iOS simulator was already launched (which may not necessarily mean you can see it in the OS X dock). You can check the state of the various simulators using the simctl command.
I.e.
xcrun simctl list devices
Then, ensure that any devices listed as "Booted" are shutdown:
xcrun simctl shutdown <device-udid-here>
Then, try running your UI tests again.
Issue
Most times, when I try to debug my custom keyboard extension, I receive the following error and then the keyboard disappears (presumably crashes, so the system removes it from screen and replaces it with the standard keyboard)
plugin com.db.Trype.TrypeKeyboard interrupted
(Note: Trype is the name of my keyboard.)
Process
I am debugging the keyboard the following way:
I have the keyboard extension as a target.
I've modified the TrypeKeyboard scheme to run my app executable on launch.
The keyboard has been added in the Simulator's Settings App.
I've tried different version of Xcode-Beta and tried restarting the simulator, computer, etc., all to a varying degree of temporary success.
Anyone else run into this error and have a suggestion?
Update:
Here is an accompanying error message. Maybe there is some way to print out more of the UserInfo?
viewServiceDidTerminateWithError:: Error Domain=_UIViewServiceInterfaceErrorDomain Code=3
"The operation couldn’t be completed. (_UIViewServiceInterfaceErrorDomain error 3.)"
UserInfo=0x7fc99c900a50 {Message=Service Connection Interrupted}
After messing around with it some more, I'm beginning to conclude this is an iOS 8/Xcode bug with the way that extensions are debugged.
Xcode sometimes seems to build project and install multiple versions of the extension keyboard into the iOS simulator. It also occasionally kills the extension and reloads it. Very strange behavior. Just sitting and staring at the debugging sidebar shows it get killed (disappear) and then relaunch.
The first is a successful launch.
The second is an unsuccessful launch where the extension appears to hang and wait to attach.
When I try to do anything in Playground, this pops up before I even finish typing a word.
Error running playground.
Failed to launch iOS stub for playground: The operation couldn’t be completed. (Mach error -308 - (ipc/mig) server died).
and when I just try to run IOS Simulator I get the following error
Unable to boot the iOS Simulator.
oh and this error just popped up
An error was encountered while running (Domain = DTiPhoneSimulatorErrorDomain, Code = 2)
I tried rebooting, I closed out and opened again, I deselected file and reselected. Just keeps happening. Anyone have a solution?
Your firewall is blocking the debugger, you need to allow it to connect:
TCP out 127.0.0.1:63748
Or allow the debugserver process open access (whichever you, or your firewall, prefer(s)).
Upon enabling it, and restarting Xcode everything should work like a charm.
Note/Update:
If you're having trouble finding, or allowing, the debugserver simply try, temporarily, disabling your firewall and restart xcode. Does the playground work? Oh, and don't forget to make sure you've got the assistant view open and the output box showing.
Currently the Xcode 6 beta needs to reside in \Applications for the playground and simulator to work. After you move it there you need to reboot.
This error popped up for me when I closed the simulator before Xcode finished attaching my application to it. Opening the simulator and running the app again solved this problem.