Thank you for reporting this issue and sharing your workaround with the community!
I can confirm this has been logged for our engineering team to review. Your local patch changing CLICK_CENTER_METHOD from "clickCenter" to "click" is helpful for other developers who may encounter the same issue.
If you have any additional details about the error or the versions you’re using, please feel free to share them here.
Thanks for reaching out and reporting this issue and patch. I’ll be following up on this issue and attempting to replicate it.
I can confirm that the usage of ‘clickCenter’ over ‘click’ was implemented intentionally by our team to align with the click function from Appium and avoid any misbehavior with elements that don’t have onClick actions. However, I’d like to dive deeper into this to identify the root cause.
To help me replicate the issue, I would kindly ask for your assistance by sharing additional information about your environment, including:
SDK/OS version
Testing device type
Any screen capture from Appium Inspector showing the tree structure of the element(s) that cannot be clicked
Any additional information that contribute to debug this issue properly.
I saw in the source that the clickCenter was intentional, however it did not appear to work. I believe the target element was an instance of Pressable
This was repro’d on a device, running BeX (not a new device, from at least a year ago).
I am unable to provide a useful tree from the inspector, I have had issue with the Appium Inspector as well. i.e. the plugin that launches in the browser does not allow me to connect, however the macOS app does – but still throws plenty of errors while the app is open and being inspected.