Skip to content
New issue

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

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

Already on GitHub? # to your account

error: no matching function for call to 'all_of' #144

Closed
vemarav opened this issue Feb 19, 2024 · 27 comments · Fixed by #146
Closed

error: no matching function for call to 'all_of' #144

vemarav opened this issue Feb 19, 2024 · 27 comments · Fixed by #146

Comments

@vemarav
Copy link

vemarav commented Feb 19, 2024

/Users/vemarav/Developer/gabit/node_modules/react-native-worklets-core/android/build/headers/rnworklets/react-native-worklets-core/WKTJsiWorklet.h:306:24: error: no matching function for call to 'all_of'

@hengkx
Copy link

hengkx commented Mar 6, 2024

upgrade xcode 15.3 same error

@Mr-Rith
Copy link

Mr-Rith commented Mar 6, 2024

same issue with Xcode 15.0, Mac m1

@Thormeard
Copy link

same issue after updating xcode to 15.3

@drookyn
Copy link

drookyn commented Mar 6, 2024

Got the same issue xcode 15.3, Mac m2.

Quickfix

Remove both std:: in L306 of WKTJsiWorklet.h: bool isCodeEmpty = all_of(_code.begin(), _code.end(), isspace);

@iagoandrei
Copy link

Same here after upgrade 15.3

@Dingenis
Copy link

Dingenis commented Mar 6, 2024

I got the same issue (after upgrading to 15.3)

@bglgwyng
Copy link
Contributor

bglgwyng commented Mar 7, 2024

Got the same issue xcode 15.3, Mac m2.

Quickfix

Remove both std:: in L306 of WKTJsiWorklet.h: bool isCodeEmpty = all_of(_code.begin(), _code.end(), isspace);

It didn't work for me. Both std::all_of and all_of are said to be not found.

@joacub
Copy link

joacub commented Mar 7, 2024

I got the same issue (after upgrading to 15.3)

same

@jarbozhang
Copy link

+1

@Thormeard
Copy link

Got the same issue xcode 15.3, Mac m2.

Quickfix

Remove both std:: in L306 of WKTJsiWorklet.h: bool isCodeEmpty = all_of(_code.begin(), _code.end(), isspace);

It didn't work for me. Both std::all_of and all_of are said to be not found.

@bglgwyng there is 2 std:: 1 is std::all_of and second one is std:: isspace. You need to remove both std::. They are in the same line.

@jdnichollsc
Copy link
Contributor

Same issue here:

Chip: Apple M2 Max
macOS: Sonoma 14.2.1
Xcode: 15.3

Error log

@ssddssde
Copy link

ssddssde commented Mar 7, 2024

+1

@Yofret-Rios
Copy link

I'm getting the same error after upgrading xcode to 15.3

@wdospinal
Copy link

Screenshot 2024-03-07 at 3 54 36 PM

I got the same issue (after upgrading to 15.3)

@HoSeopLee
Copy link

+1

@jdnichollsc
Copy link
Contributor

Submitted PR (#146) with the possible fix.

@jdnichollsc
Copy link
Contributor

Got the same issue xcode 15.3, Mac m2.

Quickfix

Remove both std:: in L306 of WKTJsiWorklet.h: bool isCodeEmpty = all_of(_code.begin(), _code.end(), isspace);

Let me know what you think about mi fix! ❤️

@Jontii
Copy link

Jontii commented Mar 10, 2024

Same here

1 similar comment
@namti
Copy link

namti commented Mar 11, 2024

Same here

@Sophearithz
Copy link

Got the same issue xcode 15.3, Mac m2.

Quickfix

Remove both std:: in L306 of WKTJsiWorklet.h: bool isCodeEmpty = all_of(_code.begin(), _code.end(), isspace);

Work for me thank ❤️

@41rumble
Copy link

Re: Quickfix

Hit and miss ... worked first build, then subsequent build failed with same error ... regenerated pods, applied your fix, and it works again

@edritech93
Copy link

still error with xcode 15.3 and "react-native-worklets-core": "^0.3.0",

@mrousavy
Copy link
Member

still error with xcode 15.3 and "react-native-worklets-core": "^0.3.0",

That's because 0.3.0 does not have the fix yet. I didn't create a new release yet.

@leveesean
Copy link

@mrousavy not sure if this is the best place to ask but are you planning on releasing this as a standalone patch or are you going to include other stuff with it? Thanks!

@leveesean
Copy link

@mrousavy not sure if this is the best place to ask but are you planning on releasing this as a standalone patch or are you going to include other stuff with it? Thanks!

oh nvm, should have looked at your releases before asking that - looks like it's included with 0.4.0 👍

@gamingumar
Copy link

Upgrading to 0.4.0 fixed the issue for me

@mrousavy
Copy link
Member

yup, already published a new release (0.4.0) with this fix

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

Successfully merging a pull request may close this issue.