-
Notifications
You must be signed in to change notification settings - Fork 463
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
'SkStream.h' file not found #55
Comments
If you're on linux, you should just have to install the |
@bolshoytoster I'm on MacOS. Let me try installing it using brew. |
NVM. I just did |
IIRC, I also did this.
|
Hi, i got same error on M1 Mac. ('SkStream.h' file not found). These commands does not solve my problem. Do you have any other ideas? |
@vedatbozkurt Can you try wiping |
still getting the same issue with the solution provided here, any idea? |
Faced with the same problem, the solution you provided did not work |
@Chasty @wq13718048209 are you still experiencing this issue? |
Is there any progress on this? I'm still get this problem after removing pods and podfile lock and also doing the repo-update |
@karlmarxlopez @iamn1ck @wq13718048209 I temporally use this hack. in example/package.json "@shopify/react-native-skia": "https://github.com/Shopify/react-native-skia/releases/download/v0.1.43-alpha/shopify-react-native-skia-0.1.43.tgz" then just
you can change it to whatever version u want. |
I also face this issue on a mac M1. With @Chasty hack, it works but can lead to inconsistencies since the examples may use features not yet released. |
Following a bit more digging, what works for me is to do all the steps to build the project locally.
|
Now my latest is still such a mistake, how to solve it |
I am also having the same issue again, or if I change my ndk dir I get this error
|
I fixed my issue by running the commands
I also had to add this to the app/build.gradle #119 |
I tried running the example, using the link to .../package and installing the alpha release but I'm getting this error.
The text was updated successfully, but these errors were encountered: