Oh man, I can feel your pain @florom. On my side, it's all Swift and the whole app is SwiftUI, DocumentGroup-based (maybe that makes a difference 🤷🏼‍♂️?)

Thanks for a rapid response @JoeKun 🙌 Its FB12168694. I'm not entirely sure how should I provide you a sysdiagnose though. Can you give me a bit more guidance on that?

Hmm, and you use ApplicationMusicPlayer specifically @nickfromsf 🤔? Well, obviously it can be something on my side, but the code that I use is pretty simple (you can see the gist that I shared in the feedback here)

Hey, I know it's been a long time ago, but I have the same issue now... Do you know whats the solution 🙏?

Yeah, I already used it 😅

(I mean URLCache configured with a /Library/Caches directory)

"NSURLCache was designed as a general purpose cache and doesn’t have the infrastructure needed to reliably support an offline mode" What do you mean by that sentence @eskimo? Let's say that we have two competing cache implementations: 1. Custom made that stores content inside of the caches directory 2. URLCache. I'm interested in the lifetime of cached data stored with these two implementations. What's the difference? My intuition is that iOS should probably treat both of these things equally (ultimately it all probably ends up in the caches directory). Is it not the case?