· One of my folders crashes the Roon app (on Mobile only)
My iPhone app is Roon version 2.62. This error previously did not occur but was introduced a couple weeks ago and will not stop. This same folder opens fine on Roon for iPad & Macbook. This same folder also does *not* crash Roon Arc on iPhone.
Tell us about your home network
· Router: Verizon CR1000B Nokia Optical Network Terminal Mac Mini M4 - MacOS Sequoia Version 15.6 Mini connected to Router via ethernet cable Storage folder contained on external SSD connected to Mac Mini
Thanks for writing in and for sharing your report!
If you haven’t yet, can you please fully remove the Roon mobile app from the issue device, and perform a fresh reinstall? Let me know if you run into the same issue.
If you do, please share the specific folder name you’re having issues with and we’ll take a closer look. Thank you!
Could you please go to your iPhone Settings, open the Roon app settings, and enable Save Logs on Startup?
After that, please restart the app, reproduce the issue, and then upload the logs for us here so we can review them.
Also, could you please try renaming the folder and then check whether the same crash still occurs?
If it does, please also send us a full list of the files inside that folder so we can review that as well. You can save the file list as a .txt file and upload it to the same link along with the logs.
Thanks for your patience. We’ve identified the relevant events in logs and see evidence of overlapping navigation events and rapid framerate changes right as the folder loads in the UI. This looks like a loop or race condition triggered by something library-specific or unique to the folders you’ve tried, given that other users can’t reproduce this yet. In order to pin this down for QA, we’ll need a little more contextual information about the folder itself.
How many items are contained within this particular folder? From the name, I assume this is quite a large volume with a significant amount of associated local metadata/tags.
If you copy a few items from this folder into a freshly-made folder, can you reproduce this issue with the new folder?
Are you able to share a screenshot of the folder itself so we can see how many items are contained therein? From what we’ve identified in logs, this is caused by a particular group of objects within the folder (track metadata, tags, etc.).