OS X 10.11.4, 2.7 Core I7, 8GB DDR3, Roon 1.6 build 416
Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
WiFi Router Netgear R7800, core computer, router and network streamer connected through gigabit switch Netgear GS205v2
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
Sonore Signature Rendu connected to Bryston BDP3 via USB
Description Of Issue
I’m getting empty history screen randomly in my iPad client. If I get it empty it stays so until I kill and restart Roon iPad app. When history screen is empty other client features working correctly. I already tried to reset my history but I’m still getting empty history after playing a number of tracks after reset.
iPad Pro 10.5, Roon 1.6 build 416. I also seen such behaviour in macOS client.
Thank you for the report here. We are aware of similar behavior occurring when the Core is rebooted while on the Overview screen (see: History Vanishes from Remote when core restarts [Ticket in]), but you mentioned that this behavior is occurring randomly for you. Can you clarify if this is the same issue or if you are performing any specific set of step(s) to get into this state?
No, I don’t perform anything specific - just browsing through library and playing tracks. I don’t touch Roon Core. I think I visit history several times, pick tracks to play and then get empty history on some subsequent visit
Can you please let me know the exact local time + date in your country when you next experience this behavior? E.g. 10:41PM on 7/15/19. I would like to take a look at the diagnostics from your iPad.
Also, if you can please track the specific set of action(s) that you performed leading up to this issue it would be appreciated (pressing any buttons, navigating to a specific screen, where you are adding tracks from, ect.).
Thank you for sharing that log output. I have discussed your case with the QA team and they have noted that we are aware of a few similar reports and that we have an open ticket regarding this issue. I can’t comment on when it will be addressed, but it is in the review queue. Thanks!