· Roon arc app started crashing frequently. Aftert reinstalling roon arc in hopes of resolving the issue I am now unable to connect to my server using arc. The app crashes durng the "first time sync" process of connecting.
Our analysis of the diagnostics report from your machine indicates that the albums Yumi Yano and Mari Iijima are broken or corrupted, which is causing them to fail to sync.
Please temporarily remove these tracks or albums from your Roon watched folders, clean up the library, and then resync Roon ARC with Roon.
Deleting the tracks (or the watched folder/storage location) won’t erase the object from the database.
To fully rule out track corruption, we’ll need to ask you to try the following:
Create a Backup of your Roon library (don’t skip this test, or you’ll need to rebuild the library from scratch)
Uninstall Roon completely by exiting Roon/RoonServer, finding your database location, identifying the RoonServer folder, and deleting it. This will fully delete the database
Open Roon; you’ll have a blank database, as if you were opening Roon for the first time. Try adding a few tracks (but not the affected albums or location) and see if ARC sync.
Restore your Backup to get your regular database back.
Let us know if we can answer any questions or elaborate here. In the meantime, we’ll inspect account diagnostics from ARC to see if we can identify an obvious failure.
I have removed the RoonServer directory and let roon recreate it from scratch. After leaving my library completely empty I was able to complete the first time sync on the roon arc app but it still crashes every time roughly 10-15 seconds after launch. That together with the fact that regular roon playback within my home network works fine leads me to believe this is an issue with the roon arc app, not a server side problem.
Thanks for the follow-up! Sorry to hear the crashing is still occurring.
From a fresh Arc dianostic report, we can see that right after the app transitions to ReadyState, it tries to reach out to Roon’s infrastructure and your Server to sync your profile and check for messages.
What the logs say: You are getting repeated TimeoutException: Timed out after 0:00:05.000000 errors for URLs like messaging.roonlabs.net, bits.roonlabs.net, and arc/discover.
The result: Roon ARC has a strict 5-second window to get a response. Because it receives nothing, the CloudSyncManager fails to resolve, locking up the app's background processes and causing it to crash shortly after launch.
We’re also seeing a specific attempt to buffer or stream a track called "Warm Ways".
The result: The app is trying to fetch a file path that it thinks is valid but is returning as an unreadable or malformed URL to the local player. If you can remove this track, that might be helpful.
And lastly, right as the app is trying to stabilize, we see this error pop up repeatedly:
error configuring usb audio usage to false
ARC is attempting to initialize its audio engine (likely trying to bypass or hand off USB routing to the OS) and failing. On mobile devices, failed hardware/driver handshakes are a notorious cause of hard application crashes.
For next steps in troubleshooting:
Timeouts to specific Roon subdomains (bits and messaging) frequently point to a DNS routing issue with your ISP. On your mobile device, try switching your Wi-Fi DNS to a public one like Cloudflare (1.1.1.1) or Google (8.8.8.8).
Disconnect any USB DACs. If you have a portable DAC or USB-C headphones plugged in, unplug them. Because of that usb audio usage error, let's see if the app stays open using just the phone's native speakers.
We’ve not seen a response in a while but we want to ensure we’ve provided the necessary assistance here. When you have a chance, please let us know the last date/time you encountered a sync failure with ARC, along with the contextual details in the post above.
Just checking in on this. Will you be able to send us the last date and time you saw the ARC sync failure, along with the context from your earlier note? If you have any additional details about what was happening when it failed, that would help us narrow it down. Thanks.
I am starting to suspect the issue is caused by a dirty custom ROM install on my phone as I started experiencing other non-arc related issues. I will get back to this topic once I find some time to do a clean install, probably later this weekend.