Roon ARC crashing on iOS (ref#M8QH39)

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Roon ARC crashing on IOS

Tell us about your home network

· pfsense no ports open, tailscale, Roon Rock on NUC ARC port 0, iphone 15 pro max. I have to reinstall roon arc every couple days else I open the roon arc app it crashes seconds after opeining. Many threads speak of large library issues. I do have a very large library. ARC app is also reported to make phone overheat. IF these are active problems it seems to me the app needs an overhual. What good is Roon if you cant use it remotely?

I think Roon’s first function is to function locally, with remote use being an extra bonus.

If this is not your intended usage it may not be the most suitable platform.

Hi @Glen_Fishbaugh,

Thanks for sharing the details — we understand how frustrating this experience can be.

We’re aware of stability issues affecting Roon ARC on iOS, particularly in setups with very large libraries, and this is something our R&D team is actively investigating. At this stage, there isn’t a confirmed timeline we can share, but the issue is on our radar and under review.

ARC is designed to complement local playback, and while it works reliably for many users, we recognize that in certain configurations it can behave inconsistently, as you’ve described.

We appreciate your patience while this is being worked on, and we’ll share updates as soon as more information becomes available.

Thank you for taking the time to report this.

Hi @Glen_Fishbaugh,

A little more context and some next steps here.

Like Roon itself, ARC needs to synchronize your music library as an object graph so it can maintain an up-to-date representation of your library and preserve parity with Roon even when you’re offline. While the data synchronized to the phone is much more compact than what exists in RoonServer, there’s a considerably lower performance ceiling for ARC than Roon when it comes to the number of objects in the library. This isn’t just because the phone has less RAM and memory - it’s actually an inherent limitation imposed by iOS/Android and their associated upstream cloud services. Large library sync failures in ARC can occur even on beefy phones with plentiful RAM, like the iPhone Pro Max series. This is because Apple and Google limit the scale of data transfer any one app can demand at any one time.

In the experience of the team, ARC performance will begin to deteriorate with libraries of about 250k tracks, but this number depends on the hardware and the makeup of the library itself. The failure will usually be during initial sync, which should never take more than about two minutes to complete successfully.

Correct me if I’m wrong, but your case is actually slightly different: ARC syncs, but then crashes during use. This isn’t the usual symptom we see for large library failures, and it suggests there might be a separate causal mechanism.

Can you please share a timestamp of the last crash you experienced within ARC for our team to pinpoint in logs?

1/10/26 @ 20:19

Hi @Glen_Fishbaugh,

The most recent diagnostics from that timestamp, unfortunately, confirm that the ARC framework can’t handle the database size. This phone operating system is throttling/killing ARC when the app demands the memory/processing required to transfer the metadata that is associated with the 400k+ tracks.

Are you encountering this problem frequently with ARC? Does it happen immediately after opening the app?

To completely guarantee performance with ARC, you’ll need to create a new version of the Roon database with a significantly smaller volume of content.

This process would entail:

  1. Deleting ARC

  2. Creating a Backup of your Roon database as it exists

  3. Creating an entirely new RoonServer (delete the old database folder and reinstall Roon)

  4. Adding in a smaller portion of your library via Watched Folders

  5. Syncing ARC and testing if it takes longer than about 5 minutes

If you can sync successfully, repeat steps 1-5 with an incrementally larger volume of your Roon library added to the Watched Folder. Repeat this until you encounter sync errors in ARC.

We recommend starting around 200k tracks and working up until you begin to notice that the initial sync takes longer than about two-five minutes to complete.

Simply removing a segment of your library from the existing database won’t reduce the actual object count contained within the database. It’s not the size of the track files in the library; the necessary indexing for the additional data (metadata, tags, play counts, etc) is beyond the limits of the smartphone operating system.

Please let us know if we can clarify further.

1 Like

We’re going to allow this thread to auto-close due to inactivity, but if you require further assistance or have any more questions, you can reactivate our discussion by submitting a new request here.