I’ve been slowly downloading my entire library to my phone’s local storage, prior to this update I could queue up many downloads and do something else while they all downloaded. I tried to do this after updating to 3.4.2 and plexamp crashed. Every time I open it now it after loading for a second or so it tries to resume the queue’d downloads and crashes immediately. I could delete all the data and reinstall but I have ~100gb downloaded already and would like to avoid that. As I’m guessing it’s related to the net network stack hopefully it can get resolved in a future update.
iOS 14.4
iPhone 11 Pro Max 512gb
If any more information would help I’d be more than happy to provide
This is considered “holding it wrong” The system isn’t designed for this, and the more you add, the more likely you are to end up running into issues, unfortunately.
However, I do see a crash reported from you which is fixed in the next release. But I would again caution you that downloading ~100GB is really, really not how Plexamp offline is intended to be used.
Oh I fully understand that I’ve jammed a square peg into a round hole, and if I thought it was an issue with the player breaking from the huge library I wouldn’t even bother posting lol. That said out of all the music players that I’ve tried to make do this, plexamp is the only one I’ve found to be quite stable even with such a huge library. All the others I’ve tried slow down and lock up/crash as you start to get a decently sized library. So kudos for scaling so well even if that was never your intent haha
Ok, so I was able to stop it queueing the downloads (and by extension the crashes) by putting it in airplane mode. From there I was able to remove the downloads and try again. I discovered it was actually a problem downloading a specific album, and when I checked it on my server I found there were a few corrupt files there. So it was just a coincidence I happened to hit those files right after the networking update lol
wow, nice move! we should still never crash under those circumstances so will still look into making it more robust, but that was clever thinking on your part