-
Notifications
You must be signed in to change notification settings - Fork 67
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
[IOS] Error saving to disk: "Could not write file: You don't have permission to save the file..." #46
Comments
This should be adressed in gl-react-native if you have any problems.. |
Hi - can you point me in the right direction of where to look so i can enable the right permissions to make this work? Currently trying using the following props/config and i'm getting a similar error, but i cannot find anything on how to fix it. <ImageCrop format={'file'} filePath={'avatar.jpg'} ref={"cropper"} image={this.state.image.uri} cropHeight={third} cropWidth={third} zoom={0} maxZoom={80} minZoom={0} panToMove={true} /> |
what i said ^^ |
Hey @Stoffern - i've looked all through the I assume it's this repo, yes? https://github.com/gre/gl-react-native-v2 Anything you could point me to would be helpful - i realise it's not in the scope of your repo, but it |
https://github.com/gre/gl-react-v2/blob/master/docs/api/Surface.md
So you use react-native-fs to provide correct paths? |
I don't, I use Expo's filesystem API, as i'm using Expo (detached to Expokit) - they produce filesystem URLs that seem to match the ones in the react-native-fs package, but i'll try and install If it works, is it okay to submit a PR to the README to provide more information? It might help a few people out. |
Hi, I'm trying to use
ImageCrop
with local file saving options:When I invoke
this.cropper.crop()
the returned Promise gets rejected "Could not write file: You don't have permission to save the file "abc.jpg"."I presume it has something to do with declared permissions in
Info.plist
but I couldn't find anything related on the web. If there is a simple answer to this it would be worth adding it to the README documentation.Somewhat related to the following: #39
The text was updated successfully, but these errors were encountered: