-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
Android - okhttp3.internal.io.FileSystem$Companion$SYSTEM$1.rename (FileSystem.java:89) crash #6123
Comments
Full stack trace? I suspect the filesystem is full. OkHttp us supposed to just stop caching when that happens. |
Also please try the latest release; we've had cache fixes since 4.5.0. |
I'm sorry for the long reply, here is the stack trace: Although, I will definitely try the lastest version, thank you! |
There are various reasons why this could be normal e.g. The phone or your app is clearing the cache, your disk is full. Can you collect this information and re-open. As is this isn't actionable, if you can confirm the cache is full and contents are not being deleted we will reopen and look more. |
Hi |
Hello, We are still seeing this crash on version 4.9.0.
Any help is greatly appreciated! Olivier |
Any chance you have two Cache instances sharing the same directory? |
If you have two serviceApi then you likely have two Cache instances sharing the same directory, this is probably the cause. See https://square.github.io/okhttp/4.x/okhttp/okhttp3/-ok-http-client/#okhttpclients-should-be-shared |
Thanks for the suggestion! We will ensure that only 1 client is created and post back if that resolves the crashes. |
These crashes keep happening:
failed to rename /data/user/0/com.package/cache/62ac51d56050cb47dea413039d3e3b67.0.tmp to /data/user/0/com.package/cache/62ac51d56050cb47dea413039d3e3b67.0
They happen randomly and not all the time, I'm unable to reproduce which makes it all the more confusing. The crashes are all similar to this one, but will sometimes be "delete" or "read"
They're happening too often to ignore. Is there a way to mitigate or fix this this? As far as I can tell, it happens on most devices. I apologize for the lack of information. We're using version 4.5.0.
The text was updated successfully, but these errors were encountered: