Hey there,
the following error message appears when running xcodebuild test command on a simulator (through ssh):
IDETestOperationsObserverDebug: Failure collecting logarchive: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.testmanagerd.control was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.testmanagerd.control was invalidated: failed at lookup with error 3 - No such process.}
2023-03-29 02:09:10.346 xcodebuild[86494:1840011] IDETestOperationsObserverDebug: Failure collecting logarchive: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.testmanagerd.control was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.testmanagerd.control was invalidated: failed at lookup with error 3 - No such process.}
2023-03-29 02:09:15.996 xcodebuild[86494:1839901] [MT] IDETestOperationsObserverDebug: 38.573 elapsed -- Testing started completed.
2023-03-29 02:09:15.996 xcodebuild[86494:1839901] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start
2023-03-29 02:09:15.996 xcodebuild[86494:1839901] [MT] IDETestOperationsObserverDebug: 38.573 sec, +38.573 sec -- end
2023-03-29 02:09:16.047 xcodebuild[86494:1839901] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot2/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-21534/IDEFoundation/Execution/Schemes/IDETestSchemeAction.m:650
Details: Error saving invocation record to resultBundlePath:Error Domain=IDEFoundationErrorDomain Code=12 "The scheme actions invocation record could not be saved due to an error." UserInfo={NSLocalizedDescription=The scheme actions invocation record could not be saved due to an error., NSUnderlyingError=0x600003889ce0 {Error Domain=(extension in IDEFoundation):__C.IDESchemeActionTestAttachment.Error Code=0 "failed to import attachment at path /Users/builder/Library/Developer/Xcode/DerivedData/DetoxTester-cgbhqpssigilfwaindwiqzhgiukb/Logs/Test/Test-DetoxTester-2023.03.29_02-08-36--0700.xcresult/Staging/1_Test/Attachments/Screenshot_1_4780DF43-975B-48B2-8DB2-34826BA5B056.jpeg, underlying error: noEntry"}}
Object: <IDETestSchemeAction: 0x7fc2991353c0>
Method: -testOperationWithSchemeOperationParameters:testManager:buildOperation:buildParameters:schemeCommand:actionRecord:testPlanRunSpecification:testRunSpecificationGroups:coverageBuildableInfos:deviceAvailableChecker:outError:actionCallbackBlock:
Thread: <_NSMainThread: 0x6000008840c0>{number = 1, name = main}
Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
Failing tests:
...
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I'm trying to use this API in my UITest suite:
https://developer.apple.com/documentation/xctest/xcuicoordinate/3551692-press
press(forDuration:thenDragTo:withVelocity:thenHoldForDuration:)
However, the holdDuration parameter has no affect and the action stops once the drag is finished (instead of keep holding the element).
I've reproduced this error with a demo application, along with a reproductive UI test and videos:
https://github.com/asafkorem/XCUITestHoldBugReproduction
Also, I do not find any reasonable workaround for the problem.
Thanks.
In my XCUITest tests, I expected to be able to scroll elements in iOS >= 15 devices (with X,Y deltas) since it’s declared in the header file as:
/**
* Scroll the view the specified pixels, x and y.
*/
@available(iOS 15.0, *)
open func scroll(byDeltaX deltaX: CGFloat, deltaY: CGFloat)
However, in the documentation website (https://developer.apple.com/documentation/xctest/xcuielement/1500758-scroll) it says under “Discussion”:
Available in macOS and in iPadOS 15 and later.
No iPhones :( Although it says nothing under “Availability”.
Calling this action when running on iPhone simulator, indeed raises the error message:
Pointer events are not supported for this device.
I’d expect this action to work on iOS as well, and not only on iPadOS. But sadly, as I mentioned, it isn't.
I made some workaround to make this "work" (partially), using XCUICoordinate but I really don't like it (since it's impossible to find an hittable coordinate without guessing or using some messy heuristics that includes frames work) and would have been happy for something more elegant.
Is there any reasonable (elegant and accurate) alternative for this, that is scrolls based on X and Y deltas?
It seems like there’s no access to many accessibility properties of UI elements exposed in XCUITest framework (XCUIElement).
Specifically, I’m trying to test the accessibility hint (accessibilityHint) of an element, but unable to do that.
Although this is what I'm missing right now, but in general there are more accessibility properties I'd like to be able to access:
accessibilityTraits
accessibilityLanguage
accessibilityActivationPoint
accessibilityPath
Is there any way to do this using XCUITest framework?
If not, why can't we access them if those are accessibility attributes? What am I missing here?
Executing /usr/bin/xcrun simctl terminate <Device UDID> <App Bundle ID> when the simulator is available but the app is not currently running causes the following error:
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=3):
Application termination failed.
FBSSystemService reported failure without an error, possibly because the app is not currently running.
This happens with Xcode 13.2 + Xcode CLI tools version 2392, however, it didn't happen in Xcode CLI tools version 2384, also Xcode 13.2, on a different machine.
First, I wonder why there's a difference between the Xcode CLI tools versions if the Xcode version is the same (both were installed from the website). Is it possible that it's related to the MacOS version (first has Monterey version 12.1 and second has Big Sur 11.6)?
Second, is this a new added error in one of the latest versions of simctl? Could we find this anywhere in a release note?