Skip to content
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 can't handle assets not managed by Expo #11

Open
YousefED opened this issue Oct 16, 2018 · 1 comment
Open

iOS can't handle assets not managed by Expo #11

YousefED opened this issue Oct 16, 2018 · 1 comment
Assignees

Comments

@YousefED
Copy link

When passing a file:// reference to resolveAsync, the file must be in the expo directory. Of not, an error will be thrown around https://github.com/expo/expo-file-system/blob/master/ios/EXFileSystem/EXFileSystem.m:639.

This is not ideal, as it prevents other libraries from easily using expo modules without depending on expo completely.

My current workaround is as follows, using react-native-fs to copy to the expo directory:

const localUri =
            expoFileSystem.FileSystem.cacheDirectory + filenameFromUri(uri);

        if (uri !== localUri) {
            // workaround for iOS
            await fs.copyFile(uri, localUri);
        }
@sjchmiela sjchmiela self-assigned this Nov 3, 2018
@reggie3
Copy link

reggie3 commented Apr 14, 2019

I'm running into the same problem trying to adapt react-native-webview-leaflet and react-native-webview-quill-js to use this library. Both packages work well in their standalone demo apps, but the webviews in my packages are unable to find their index.html files when the packages are included in a separate application. Is this an issue that will be addressed at some point?

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

No branches or pull requests

3 participants