· Can’t reach my Server, remotes or ARC
· Other ARC issues
· ARC initialed crush after 15 sec. of launching
· Router: Asus RT-AX88U + Netgear 8 Port Switch
VPN: Tailscale
Note: It happens after upgrading to 1.71. Previous version works perfectly.
Hello @Oliver_Kuo !
We’re sorry to see you are facing this problem.
Could you please assist us with collecting the information for investigation ?
We’d like to ask you to connect your iPhone to the Mac and open “Console” app.
Then please start streaming data from your iPhone like this:
While the logs are being recorder please reproduce the problem and after that please pause the streaming and select all entries that were recorded and export it to some .txt like file and upload it to our logs storage.
Also, can you please clarify at what condition does it crash ? It does not load to the main page or it crashes inside the app ?
Thanks!
Regards.
Thank you, Alex, for your quick response,
I have uploaded RoonARCErrorLog.txt to logs storage as requested.
APP crashes while ARC launches EVERY TIME and never syncs successfully to server after upgrading to the new version.
If you need more information, please let me know.
Thanks again.
Good day @Oliver_Kuo !
Thanks for the log.
I’m going to open an internal ticket for this problem to our developers.
Could you please assist also by recording a video of the problem and uploading it here ?
Thanks!
Yes Alex, two videos are up for your reference:
RoonARCErrorPart1 - Launch and crash after 20 secs.
RoonARCErrorPart2 - APP are at the background. Re-up and crash after 20+ secs.
Hi @Oliver_Kuo,
Unfortunately, you’re encountering an inherent limitation with ARC due to the size of your Roon library.
When a Roon library grows beyond roughly ~250 thousand tracks, ARC may struggle to operate reliably, and in some cases, it may not be able to complete its initial sync with your RoonServer at all. Our diagnostic servers indicate that your Roon libary is well over one million tracks.
To support offline use and ensure consistency with your main Roon database, ARC must build and maintain a condensed local version of your library on the phone. At very large library sizes, this becomes challenging for two reasons. First, the sheer complexity and volume of library data that needs to be synchronized places a heavy load on the mobile device. Second, iOS (and the underlying services ARC depends on) enforces practical limits on how much data a single app can transfer and process in one continuous operation.
As a result, while ARC works well for most libraries, massive collections can exceed what mobile platforms are realistically able to handle, even when everything on the network side is functioning correctly.
Your setup and library are very much at the extreme end of what ARC was designed to accommodate, and the behavior you’re seeing isn’t a reflection of anything being misconfigured on your end. ARC continues to improve with each release, and large libraries are an active area of ongoing optimization. For now, the sole path forward here is a heavy-handed one - you’ll need to create a new version of your Roon database with a significantly smaller database that you rely on to sync with ARC. The remainder of your collection would need to reside in a location that you only intermittently add to Roon as a Watched Folder (keep in mind that the database will retain the objects even if you’ve deleted the files).
Please let us know if we can clarify any details.
Thank you, Connor, for detailed explanation of what I have encountered.
While you suggest to create slim-sized database and try to sync both if anything modified, in reality, I am hesitated to do that at such a large volume of my collection working on. Your system is very good at desktop devices. It would not be necessary to create another D/B for ARC only.
Because previous version of ARC is working well for this issue, could I downgrade to old version at iOS?
Thank you!
Hello @Oliver_Kuo,
Thank you for your understanding.
The behavior you’re seeing is a known limitation when ARC is used with extremely large libraries, and your case is very helpful to our team in that regard. ARC’s initial sync process needs to build a local representation of your library on the phone, and at multi-million track counts this can exceed what iOS and ARC can reliably process in one session.
Our R&D team is actively working on improvements in this area, including better handling of very large libraries and more resilient sync behavior. Unfortunately, at this time there isn’t a supported way to bypass this limitation or to downgrade ARC to an earlier iOS version.
For now, the only viable workaround remains using a smaller ARC-friendly database if mobile access is required. We know this is far from ideal, and we appreciate your patience while the team continues to improve ARC’s scalability.
Please let us know if you have any other questions or need clarification.
To add some additional context here - a one-million track library is an order of magnitude larger than consumer systems are built to accommodate. This track count is approaching the size of a digital archive hosted by a small radio station or streaming service. We can provide recommendations for how ARC might work in this scenario, but we’re also severely limited by the Apple/Android and cloud ecosystems in which the app operates. Thank you for your understanding.
Thank you, Vadim, Connor, for your detailed explanation. I am just a music-loving guy for personal pleasure.
I hope your next version of ARC would work well, as previous version did.
Hi @Oliver_Kuo,
It’s our goal to make ARC funcion for all Roon users. We’d love to eventually reach a point where the app can easily handle a library of this size, and we encourage you to continue to post in Feedback and here in Support about your experience with the app. This is particularly true if you encounter and other novel symptoms or problems with the app.
Thank you again. You can reach us anytime here, and you can create a post without the intake form in Roon Software Discussion at any time.