Are you on testflight? I've just added a new option to clear/manage cache at the bottom of Settings/General, so you could test that (still an experimental feature though)
Yes. I set it to 4gigs to see how fast it fills up and clear it. Will report back. I thought I set it to 4 yesterday, but noticed it was at 2gigs. Since yesterday, which I used the app for hours, it only filled up ~260mb. Whatever the issue was though, it seems to be resolved.
I do appreciate the work you do and quickness in creating a solution.
Not sure, but I saw Liftoff had like 68gigs. Both were test flight apps. Now Avelon seem to have settled at 2.6gigs. I did update to 17, then17.1, then 17.2. The issue may be resolved.
13 replies
Are you on testflight? I've just added a new option to clear/manage cache at the bottom of Settings/General, so you could test that (still an experimental feature though)
Yes. I set it to 4gigs to see how fast it fills up and clear it. Will report back. I thought I set it to 4 yesterday, but noticed it was at 2gigs. Since yesterday, which I used the app for hours, it only filled up ~260mb. Whatever the issue was though, it seems to be resolved.
I do appreciate the work you do and quickness in creating a solution.
Thanks, glad to hear it! The cache has a time expiration too, so you'll probably have to use the app a whole lot to reach 4GB
Challenge accepted!!
Thanks! I was up to 9.7 GB on the App Store version. Just switched to TestFlight. Will report if the issue comes back.
I’ve had this iPhone for about two years, yet Avelon, which I downloaded less than a week ago, is the 3rd most user of storage. What gives?
I don’t and it’s up to 8.94 GB
Needs to lower its cache size for sure.
Same issue. Hope it will be fixed soon.
That’s really odd. I have been using it pretty regularly for a few weeks and have 65.1 MB total. I don’t think I changed any settings with it.
Maybe because I’m on iOS 17?
Not sure, but I saw Liftoff had like 68gigs. Both were test flight apps. Now Avelon seem to have settled at 2.6gigs. I did update to 17, then17.1, then 17.2. The issue may be resolved.
This is a iOS 17 bug
As in showing false values? Or wrong cache management or something?