I faced that f-droid uses 1.7 GB of storage. After deleting it and using it for a day again. I am at a more reasonable 157MB. Is this big size expected behavior? I do not use any extra repos or something like that. I only configure the theme of the app, so deleting the data regulary is no big hassle for me.
it keeps the apps you download cached, it should automatically clear itself after some time period
In theory, but… @funny0facer try to disable battery optimisations for F-Droid, setup a low “keep packages” (albeit the default should be ok), keep an eye on it
when I read “cached” I would expect it in the “cache” size and not in the user data.
I changed battery optimisation now. i will keep an eye on it.
It’s “complicated” it gets copied there for install
My theory is that F-Droid gets killed (hence me asking about excluding from battery opts) and does not get a chance to cleanup
This issue is a never ending headache
F-Droid client should store apps in cache storage and not in user data
This is why any sane person will just use third party clients.
To disable the battery optimization for F-Droid did work. The userdata did get cleared.
So thanks for pointing me there
Which of these issues is best place tracking a fix? I can understand copying it there temporarily for install, but not deleting that immediately upon detecting the app is up-to-date, while keeping the original cached copy as long as directed by preference or when user chooses to clear app cache.
I guess they might get fixed both but no one is working on that afaik