Opening 'file://' URLs

[divan]

Hi,

first of all, thanks for the fantastic plugin – it's truly the best web browser Flutter plugin out there!

So I need to open both "normal" urls (http://) and local files (file://). Currently I'm testing only on iOS and the problem I see is that opening local file via file:// URL fails on the device (but works in a simulator). Error is The operation couldn't be completed. Operation not permitted.

I've read in docs that for opening local files we should use loadHTMLString:

Use the loadHTMLString(:baseURL:) method to begin loading local HTML files or the load(:) method to begin loading web content.

This, however, requires a lot of hassle with opening and reading file from FS, figuring out correct MIME type (I need just PDFs and Images, but everything that webkit supports should work ideally) and so on.

I initially tried initialFile option, until read that it's actually initialAsset (rename, perhapse?). So maybe it's worth implement initialFile for local files (not only assets)?

Or maybe there is a better way to load local resources? (I don't have much experience with mobile dev, so may be missing some obvious things)

Thanks in advance!

[micsanbr]

I can confirm this. I am able to load local files in Android (downloaded from firebase to the application directory on the device) using initialUrl, but the same does not work on iOS.
Error: (1) The operation couldn't be completed. Operation not permitted.

[shodafl]

@micsan13br Hi! how do you import local files on android?

[micsanbr]

@shodafl my reply to this issue goes back to 2019. I don't know if this still applies to the latest version or what was this about at all.

[github-actions]

This issue is stale and has been automatically closed because it has been open for more than 365 days with no activity. Please reopen a new issue if you still have it.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug and a minimal reproduction of the issue.