fix(android): tap event on android API>31

[ericschaal]

Description

• This pull request addresses the issue 3762 described here: Android API 32, 33 (v12): .tap() acts like tap+hold #3762

In this pull request, I have updated obtainUpEvent in com.wix.detox.espresso.action.common.MotionEvent to match more closely the implementation of obtainUpEvent in androidx.test.espresso.action.MotionEvents.

For features/enhancements:

• I have added/updated the relevant references in the documentation files.

For API changes:

• I have made the necessary changes in the types index file.

[noomorph]

Thanks for your contribution!

Our Android guys are currently unavailable, but I'll try to review and suggest a test plan for this PR. It might take a few days.

Could you please tell me whether this PR should work with lower Android API versions? Did you have a chance to check both <=31 and >31?

[ericschaal]

Thanks for your contribution!

Our Android guys are currently unavailable, but I'll try to review and suggest a test plan for this PR. It might take a few days.

Could you please tell me whether this PR should work with lower Android API versions? Did you have a chance to check both <=31 and >31?

My thoughts are with everyone affected by the ongoing conflicts...

Thank you for taking a look despite the circumstances. I've tested the changes on both Android API versions 34 and 29. Please let me know if there's anything else you need.

[noomorph]

Okay, I see. If you don't mind, I'll create a prerelease tomorrow (in about 14-15 hours), and let's invite volunteers to give it a try.

I'll also try to run the pre-release on our mobile projects and see how it goes.

If no complaints are detected, we'll merge that after a week of dogfooding (next Thursday, for example).

[noomorph]

The smoke version is available as [email protected] on NPM.

[d4vidi]

LGTM. Thank you.

[noomorph]

✅ The fix is available in [email protected].