Then you miss read a lot of comments, most people want a stable cache to be sure that the media they cache are available when they want to play it and not removed because they cached the one more song …
That’s the whole point of an offline first app, having a constant controlled offline behavior…
Rolling cache is rolling, you can’t enable automatic cache to the rolling cache because this can’t work properly.
Have a cache size of 1Gb, enable rolling cache on 2 playlists that have more than 1 Gb of data.
Then what? the app keeps removing and downloading again the files since it can’t fill the cache? It randomly choose what is cached and what not? There’s no proper solution, if you say I want X cached but the result is that a part of X is not cached, then it’s a broken choice and implementation …
So to put things in rolling cache you either use the automatic rule that put played media there or you manually put things there.
Everything is documented and is logical and predictable.