it looks like the most complicated part there would be to make NSPredicate work properly with custom attributes. I knew it was going to explode some day.

Basically we need to parse the initial predicate expression as a string and transform it into a block, where we could process custom snapshot properties (e.g. these starting with wd...)

@mykola-mokhnach we can instead use class_addMethod in runtime for XCElementSnapshot and add our attributes.
I've tested it in a quick and dirty fashion by exposing wdLabel and isWDVisible from XCUIElement+FBWebDriverAttributes and added the following code to FBXCElementSnapshotWrapper:

+ (void)load
{
  Class XCElementSnapshotCls = objc_lookUpClass("XCElementSnapshot");
  
  // for wdLabel
  Method wdLabelMethod = class_getInstanceMethod([FBXCElementSnapshotWrapper class], @selector(wdLabel));
  class_addMethod(XCElementSnapshotCls, @selector(wdLabel), method_getImplementation(wdLabelMethod), method_getTypeEncoding(wdLabelMethod));
  
  // for isWDVisible
  Method isWdVisibleMethod = class_getInstanceMethod([FBXCElementSnapshotWrapper class], @selector(isWDVisible));
  class_addMethod(XCElementSnapshotCls, @selector(isWDVisible), method_getImplementation(isWdVisibleMethod), method_getTypeEncoding(isWdVisibleMethod));
}

For isWDVisible I also had to modify it to the following (since fb_isVisible is not defined for XCElementSnapshot, but on second thought we can also add this method directly as well as above):

- (BOOL)isWDVisible
{
  return [[FBXCElementSnapshotWrapper alloc] initWithSnapshot:self].fb_isVisible;
}

What about the below fastlane version?
https://dev.azure.com/AppiumCI/Appium%20CI/_build/results?buildId=20298&view=logs&j=b0b7e611-f24f-5025-cfe1-d0e5eed5ba7f&t=1db81a0e-a352-5921-8e54-3d6dffa5f477

Fetching fastlane 2.162.0
Installing fastlane 2.162.0

let me try 2.162.0...

Thanks @KazuCocoa
I'd say we are happy with this version for now + Ruby2 and stay with it until possible.

One way we found to link with XCTAutomationSupport was to use a fake dylib with a name from the allowed names and reexport XCTAutomationSupport through -reexport_framework/-reexport_library linker flag. I made an example here.

A bit of a hack but maybe that's something that you would want to employ?

Thanks for the fix @mykola-mokhnach!

Considering appium 2 is in beta, are there any plans to fix this for appium 1? (it still pulls in appium-webdriveragent v3, fix is in v4)

(couple of workarounds: use your old ~/Library/Developer/Xcode/DerivedData/WebDriverAgent-... dir built with xcode 13 (rename to match expected), or pin v4 of appium-webdriveragent)

@pwfcurry no, appium 1 is now unsupported. appium 2 is only in beta because the documentation hasn't been ready for a release. but in terms of its suitability for production use code-wise, it has been our only supported version for some time now. so it would make sense to update to appium 2 to take advantage of any fixes.