Posts

Post not yet marked as solved
2 Replies
1.6k Views
After taking Xcode 11 install, tests that used the pickerWheels.adjust method fail as that method no longer works. UI tests fail giving messageAssertion Failure: <unknown>:0: Unable to find current value '(null)' in possible values 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 00 for the picker wheel PickerWheelhowever if I run in debug mode, placing a break point and enter the command in debugger in form ofpo app.datePickers["IDOFPICKERWHEEL"].pickerWheels.element(boundBy: 1).adjust(toPickerWheelValue: '19')The debugger prints out the Assertion failure message as above for the first time that I enter the command, but if I repeat the command no Assertion Failure message or any other error message. It prints a series of Find and Synthesize Event messages and then stops. The pickerwheel does not change in response to either of the commands (current value is 18 by the way). Log printout from debugger below(lldb) po app.datePickers["acid.pickerWheel.flightTime"].pickerWheels.element(boundBy: 1).adjust(toPickerWheelValue: "19") t = 53.23s Set value of PickerWheel to 19 t = 53.24s Wait for com.flyapg.ipreflight to idle t = 53.72s Find the PickerWheel t = 53.72s Requesting snapshot of accessibility hierarchy for app with pid 688 t = 53.84s Find: Descendants matching type DatePicker t = 53.84s Find: Elements matching predicate '"acid.pickerWheel.flightTime" IN identifiers' t = 53.84s Find: Descendants matching type PickerWheel t = 53.85s Find: Element at index 1 t = 53.85s Check for interrupting elements affecting PickerWheel t = 53.85s Synthesize event t = 53.98s Assertion Failure: <unknown>:0: Unable to find current value '(null)' in possible values 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 00 for the picker wheel PickerWheelerror: Execution was interrupted, reason: internal ObjC exception breakpoint(-14)..The process has been returned to the state before expression evaluation.(lldb) po app.datePickers["acid.pickerWheel.flightTime"].pickerWheels.element(boundBy: 1).adjust(toPickerWheelValue: "19") t = 60.79s Set value of PickerWheel to 19 t = 60.80s Wait for com.flyapg.ipreflight to idle t = 61.26s Find the PickerWheel t = 61.26s Requesting snapshot of accessibility hierarchy for app with pid 688 t = 61.37s Find: Descendants matching type DatePicker t = 61.37s Find: Elements matching predicate '"acid.pickerWheel.flightTime" IN identifiers' t = 61.37s Find: Descendants matching type PickerWheel t = 61.37s Find: Element at index 1 t = 61.38s Check for interrupting elements affecting PickerWheel t = 61.38s Synthesize event t = 61.43s Wait for com.flyapg.ipreflight to idle(lldb)I can say that in general I have seen problems with accessibilityValue. the property accessibiltyValue is present if I view the application in the Debug View Heirarchy or the Accessibilty Inspector, but that property is no longer visible to the UI test proxy. Attempts to read the value of UI elements by value now always return nil, even if the value is set. I imagine that this pickerwheel problem is related. Possibly not.
Posted
by APGtest.
Last updated
.