Closed ndbroadbent closed 1 month ago
It works if I replace find_by_id
with find
. (Just have to disable our Capybara/SpecificFinders
RuboCop rule, which prefers find_by_id
.)
I have dropped the ~>
limitation as 3.1.0 first. The version will let users install higher appium_lib_core and appium_lib.
I guess... in the case, https://github.com/appium/appium_capybara/blob/master/lib/appium_capybara/ext/selector_query_ext.rb#L37 was called. It should be raise an exception based on the original capybara code. https://github.com/teamcapybara/capybara/blob/a7ebe1216f8d65f2e96c170437a732777353a81d/lib/capybara/queries/selector_query.rb#L247
or some method overrode. Please try out with latest one first. I did some modifications between them before.
I also wondered if https://github.com/appium/appium_capybara/blob/master/example/spec/capybara_init.rb#L18 would affect unexpected method overrode (which is "true" by default, it means the appiun's driver will be used with $
https://github.com/appium/ruby_lib/blob/4a74c60937e66bf028a66e4f05a324ce8b2077ce/lib/appium_lib/driver.rb#L200
Thank you for dropping the ~>
limitation, that helped a lot! I'm getting much further now, but will open a new issue for a different crash I'm seeing.
Sure, closing this ticket
Hi there, I'm seeing this error when I use appium_capybara 1.10.0. I tried updating to 3.0.0 but it looks like some dependency versions get downgraded:
Here's the issue with
appium_capybara
1.10.0:I think the following can be ignored, even though it's the latest version of appium_capybara:
With appium_capybara 3.0.0, I get this crash due to the older version of appium_lib_core (5.2.0 instead of 9.1.3):