Roon Core Machine
Mac mini 2.7GHz i7, 8GB, MacOS 10.13.6
Networking Gear & Setup Details
Hm… for the purpose of this issue, the iOS devices go through a TP link access point (wifi) and a couple of Netgear switches to reach the Roon core.
Connected Audio Devices
- Matrix Mini-i Pro3 - Ethernet
- Sonos Play:5 - Wifi
- RoPieee endpoint - Ethernet
Number of Tracks in Library
Roughly 26000 tracks
Description of Issue
I see odd behavior on my iOS devices, one late-model iPad Pro and an iPhone 12. Generally, the Roon client works fine on both devices. The iPad in particular I use most days, all day long - it sits next to me while I work at my desk, and when I don’t need it for anything else it usually displays the Roon play queue most of the time as I listen to music during the day. There is usually no trouble at all during this entire time. The iPhone usually works fine as well - I don’t use it as often, but when I do there’s no trouble with this either.
Here’s the weird thing though. Sometimes when I start Roon on one of these iOS devices, it comes up for about two seconds or so, and then it dies. I can try this again and again and it dies every time. It comes up in the same “place” every time - i.e. the last album I looked at, or the play queue, or whatever.
For the short moment before it dies, the app is actually usable. For example, I can quickly try to hit the Play or Pause button while it’s visible, and that works - it plays or pauses, then the app dies again. However, this is also the workaround I have found for the problem: while the app is up, I hit something that changes the “mode” the app is in. For instance, if I’m not in the play queue view yet, I try to hit that button - and when I manage to do this in time, the view changes, the app runs properly and in all likelihood works correctly the rest of the day, including any number of restarts.
Unfortunately the “special action” required to prevent the app crashing is not always the same. I work in software, I know what to look out for … and I haven’t been able to identify the pattern to this problem, even though I’ve been seeing it for months now. So I’m wondering - is there a log file somewhere? Some kind of tracing facility that would allow me to see what’s going on when the crashes occur? Any other ideas?
Oh, and with all the questions above I didn’t see the place where I would enter the version of the Roon client: 1.8 (build 831) - but I remember updating at least twice since I first saw this problem, so it’s probably not very specific to this version.
