Skip to content

fix: [Closes #164] Remove third argument to jSTouchDispatcher.handleTouchEvent call (which causes a build error on Android) #194

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

brandonballinger
Copy link

@brandonballinger brandonballinger commented Jul 2, 2025

This fixed the build issue on Android reported here for me: #164

Initially I suspected the bug was caused by a mismatch in react native versions. But I took a look at the commit history for JSTouchDispatcher in react-native, and that file hasn't been modified since 2018 and I can't find a version of handleTouchEvent which accepts the third argument used here. So I'm not entirely sure how the original code worked on Android.

Copy link

vercel bot commented Jul 2, 2025

@brandonballinger is attempting to deploy a commit to the Jovanni's projects Team on Vercel.

A member of the Team first needs to authorize it.

Copy link

codeclimate bot commented Jul 2, 2025

Code Climate has analyzed commit 1690ace and detected 0 issues on this pull request.

View more on Code Climate.

@lovegaoshi
Copy link

the method indeed exists (exists b4 the kotlin migration too).

though this might be fine as react-native-screens also uses the 2 arg overload (which calls the 3 one with reactContext=null)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants