Empty history screen in iPad client - [Ticket In]

(Vladimir) #1

Core Machine (Operating system/System info/Roon build number)

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.

(Noris) #3

Hi @vladimirkl,

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?

(Vladimir) #4

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

(Noris) #5

Hi @vladimirkl,

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.).

(Vladimir) #6

@noris I just got empty history screen in macOS client too. Here is what I have in client log after several attempts to open history screen
07/18 20:06:55 Debug: UI-FWD: mode: albumdetails
07/18 20:06:55 Debug: GMS: saving nav stack
07/18 20:06:55 Debug: UI-NAV: album details / album: [object Sooloos_Broker_Api_AlbumLite_Proxy] / bookmarkdata:
07/18 20:06:55 Debug: GMS: done saving nav stack
07/18 20:06:59 Debug: UI-FWD: mode: historybrowser
07/18 20:06:59 Debug: GMS: saving nav stack
07/18 20:06:59 Debug: UI-NAV: history browser / focus: / bookmarkdata:
07/18 20:06:59 Debug: GMS: done saving nav stack
07/18 20:07:01 Info: [stats] 5201mb Virtual, 233mb Physical, 162mb Managed, 51 Threads, FDs
07/18 20:07:16 Info: [stats] 5198mb Virtual, 234mb Physical, 164mb Managed, 49 Threads, FDs
07/18 20:07:23 Debug: UI-BACK: mode: albumdetails
07/18 20:07:23 Debug: GMS: saving nav stack
07/18 20:07:23 Debug: GMS: done saving nav stack
07/18 20:07:24 Debug: UI-BACK: mode: albumbrowser
07/18 20:07:24 Debug: GMS: saving nav stack
07/18 20:07:24 Debug: GMS: done saving nav stack
07/18 20:07:27 Debug: UI-FWD: mode: historybrowser
07/18 20:07:27 Debug: GMS: saving nav stack
07/18 20:07:27 Debug: UI-NAV: history browser / focus: / bookmarkdata:
07/18 20:07:27 Debug: GMS: done saving nav stack
07/18 20:07:30 Debug: UI-BACK: mode: albumbrowser
07/18 20:07:30 Debug: GMS: saving nav stack
07/18 20:07:30 Debug: GMS: done saving nav stack
07/18 20:07:31 Info: [stats] 5203mb Virtual, 237mb Physical, 165mb Managed, 51 Threads, FDs
07/18 20:07:41 Debug: UI-FWD: mode: albumdetails
07/18 20:07:41 Debug: GMS: saving nav stack
07/18 20:07:41 Debug: UI-NAV: album details / album: [object Sooloos_Broker_Api_AlbumLite_Proxy] / bookmarkdata:
07/18 20:07:41 Debug: GMS: done saving nav stack
07/18 20:07:43 Debug: GMS: saving nav stack
07/18 20:07:43 Debug: GMS: trying to save nav stack, but nav stack stuff was in progress
07/18 20:07:43 Debug: GMS: done saving nav stack

(Noris) #7

Hi @vladimirkl,

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!