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

DOMException: The requested file could not be read, typically due to permission problems that have occurred after a reference to a file was acquired #14

Closed
yuwei336 opened this issue Aug 13, 2021 · 3 comments

Comments

@yuwei336
Copy link

When I flash a zip file, if read smaill file, it will be ok. but if read big file just like product.img(522MB) it will throw: "
ui.js:107 Uncaught (in promise) DOMException: The requested file could not be read, typically due to permission problems that have occurred after a reference to a file was acquired.
flashSelectedFactoryZip @ ui.js:107
async function (async)
flashSelectedFactoryZip @ ui.js:105"

I think it's not permission related issues.

@kdrag0n
Copy link
Owner

kdrag0n commented Aug 16, 2021

Yes, it's not a permission issue. This is the error message shown by android-webinstall for that exception:

There isn’t enough storage space available to download and unpack the OS. You need at least 5 GB free.

If you’re not low on storage, this is caused by using an incognito window or guest browser profile. These profiles have very low storage limits, so installing from them isn’t possible.

To fix this, switch to a normal browser profile and try again.

@kdrag0n kdrag0n closed this as completed Aug 16, 2021
@davigamer987
Copy link

I'm also having this issue, I'm using kiwi browser so I can access debug console, I'm on a normal profile and I can't flash anything larger than 2gb, any way to get around this ?

@kdrag0n
Copy link
Owner

kdrag0n commented Dec 3, 2022

I'm also having this issue, I'm using kiwi browser so I can access debug console, I'm on a normal profile and I can't flash anything larger than 2gb, any way to get around this ?

Memory usage is a known issue with no easy fix. #27

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