· With the latest update Arc crashes/freezes and makes the phone hot (iPhone 13, latest OS). The normal workaround with deleting the app and reinstalling initially works on wifi, but just connecting once to 5G the app is wrecked and won't work on wifi either after that.
Tell us about your home network
· ASUS RT-AX92U, nuc connected with ethernet, static IP, no VPN.
Yes my library is large, but it has been that way since the beginning of Arc and has worked fine using the above solution of deleting the app and reinstalling every so often (usually after a core update or larger library change).
Deleted and reinstalled the app again now at midnight CET using wifi for the initial sync. The app seemed to work fine and the phone was cool to the touch. Then I switched over to cellular and the phone got really really hot but did not crash. Went to bed and now this morning around 6:45 CET on the way to work I started the app again and it froze after a few minutes.
Usually don’t download any tracks locally for my commute, only for longer cross country trips where the cellular service is horrendous. I have about 40GB of free space on the phone.
Cellular service here in central Stockholm is most likely as good as it gets (outside of Japan). , full bars this morning when it crashed.
Would you kindly provide the exact timestamp when the next time your iPhone will heat up on the cellular data? We will review the diagnostic report to understand what background activity is causing it.
Did a fresh install over wifi again and switched over to cellular and by 19:25 central european time the phone was very hot. The app didn’t freeze, but it was draining the battery fast (yesterday it sucked 5% of the battery in 4 minutes).
Thank you for providing that timestamp. We have pulled the diagnostic logs from 19:25 CET and reviewed the activity.
What we are seeing in the logs during this time is a massive background sync. Because your Roon library is exceptionally large (roughly 240,000 tracks), ARC has to do a tremendous amount of heavy lifting to build its local database structure, fetch metadata, and cache images.
When this heavy background processing is occurring, the iPhone’s processor and cellular modem are both running at maximum capacity simultaneously. This dual workload is exactly what causes the phone to get very hot and drain the battery so rapidly (like the 5% drop in 4 minutes you observed). For a library of your size, this intense resource usage during the initial sync phase is actually expected behavior.
To find the root cause of the app breaking, we need to catch the exact moment the application actually fails during the day-to-day usage after the initial sync.
Could you please continue using ARC on 5G until it completely freezes or crashes as you initially reported, and share the exact time that specific event happens?
(Tip: To avoid the massive battery drain on 5G after a fresh install, we highly recommend leaving the ARC app open while your phone is plugged into a charger on Wi-Fi overnight. This allows the massive initial sync to finish completely before you take it on the go.)
So some timestamps; Mars 14 at 10:45 am CET the app stopped playing music, started it again and by 10:47 when I checked again the GUI was frozen (music still playing).
I reinstalled the app again this morning and left it running for 40+ minutes to see if the sync was able to finish before heading out, not as long as you suggested but it did the trick and it worked like normal for the hour or two I was out.
As I mentioned previously, we are actively investigating a known issue that affects exceptionally large libraries, and our R&D team is working hard on performance improvements. I have attached your logs, hardware specifications, and reported symptoms directly to the internal tracking ticket for our developers to review.
At this moment, no additional information is needed from your end. I am going to place this ticket on hold while the team continues their work, but I will be sure to reach back out to you as soon as we have an update to share or if we need any further details.
Thank you for your patience and for helping us track this down!
