You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 16, 2019. It is now read-only.
On Android, the fs.asset('path/to/file') function returns a path that when used with fs functions, works on files embedded in the APK app bundle, specifically from the app/src/main/assets directory. This works great.
(reference for Java implementation)
On iOS, I expected that fs.asset('path/to/file') would return a path that allows access to files embedded in the IPA app bundle, e.g. ${fs.dirs.MainBundleDir}/path/to/file.
However it actually returns a path that allows access to the camera roll.
(reference in js)
This is easy to work around of course.
It'd be a breaking change to adjust this (perhaps add new function fs.js | cameraRoll(path:string)?
I can send a PR if this is useful.
The text was updated successfully, but these errors were encountered:
On Android, the fs.asset('path/to/file') function returns a path that when used with fs functions, works on files embedded in the APK app bundle, specifically from the
app/src/main/assets
directory. This works great.(reference for Java implementation)
On iOS, I expected that fs.asset('path/to/file') would return a path that allows access to files embedded in the IPA app bundle, e.g.
${fs.dirs.MainBundleDir}/path/to/file
.However it actually returns a path that allows access to the camera roll.
(reference in js)
This is easy to work around of course.
It'd be a breaking change to adjust this (perhaps add new function fs.js | cameraRoll(path:string)?
I can send a PR if this is useful.
The text was updated successfully, but these errors were encountered: