[Potential fix in #1465] Roon B1463 ARC B301 Infinite duplications of ARC reproductions in my History

[Daniele_Piancastelli (Dani)]

It’s happening again with the latest Roon/ARC build. Every time I open ARC, the playback recordings multiply endlessly

ARC Build 230 & Roon 2.0 Build 1362 Feedback

Something strange is also happening in the History and play count. With the new build 1358 it is endlessly duplicating tracks (seems like every time you exit and enter ARC or scroll from top to bottom to refresh). Here are some screens and a video. Video [1] [2] [3]

example timestamp 22.23 CET

[oleh (Oleh Ilash)]

Thank you @Daniele_Piancastelli! We could reproduce the issue and sent the ticket to the dev team.

[gsuzor91]

In case this helps with troubleshooting…

I don’t think I’ve had duplicate history entries before, but I now see many duplicates in my history from yesterday. I was on ARC 300 at the time with everything else on B1463.

I’m on Android 14 and ARC 301 was not installing via the play store as of an hour ago. I’ve now installed 301 from the apk download. After I installed the apk, I rebooted my server to be safe. I performed these actions before I realized I had any duplicates.

Now, after the ARC 301 update and server reboot, the album I just played is showing correctly in my history. I will keep an eye on the history to see if duplicates make another appearance.

[Daniele_Piancastelli (Dani)]

@oleh any info on the ticket resolution times?
It’s hard to take care these uncontrolled duplications at bay.
I have to use ARC in offline mode with the downloaded albums because as soon as it connects the duplication occurs and I have to clean the history section

[oleh (Oleh Ilash)]

@Daniele_Piancastelli, This is expected to be fixed in the next release. Sorry for the inconvenience you’re facing now.

[gsuzor91]

After I posted my previous comment, I started questioning exactly when I updated ARC and my server. I started to look through my logs to verify and I believe what I stated is generally correct.

@oleh As I was looking through my logs, I uncovered a mobilesync error (see details at the end) that may or may not be related. This happened when my server was on EA 1463 and ARC was on production 300. (At that point I was on the ARC EA (beta) release in the Google Play Store, but the production 300 release bumped me up and I just left it there.)

The error I found went away after I installed the ARC EA 301 APK (server still on EA 1463). Since I had to uninstall my play store 300 version and I essentially had to do a fresh install of ARC, I believe this reset ARC in a way that removed the “syncing listen later…” action it seemed to be getting stuck on.

I’m also wondering if this could be related to @J_B 's post since a lot of start/stops were mentioned and this sounds like the “syncing listen later…” error I see in my logs.

Play Counts Seem Off in ARC

After a few weeks of using ARC after the Tailscale, things have been going pretty well, there are a few things and one of them is play counts. I tend to listen through classical composers “complete works” albums while I work. However, I cannot see any play counts in ARC, so it is difficult to pick up where I left off in ARC. Instead I need to note which disc or track I’m on and continue from there. Now, that is a minor inconvenience that I can work-around that I hope RoonLabs will eventually fix…

Issue Details and Log snippets

The pattern I found was repeating entries such as this:

09/30 20:42:17 Trace: [library/mobilesync] syncing recent play for album 200:9:34504

Then it was trying to sync two albums, with the one I listed above included:

10/01 00:45:18 Trace: [library/mobilesync] syncing recent play for album 200:9:34504
10/01 00:45:18 Trace: [library/mobilesync] syncing recent play for album 47:9:380463

Then three:

10/01 02:29:09 Trace: [library/mobilesync] syncing recent play for album 200:9:34504
10/01 02:29:09 Trace: [library/mobilesync] syncing recent play for album 47:9:380463
10/01 02:29:09 Trace: [library/mobilesync] syncing recent play for album 47:9:384303

Each time it tried to sync when the recent plays were repeating, it would fail with an error such as:

09/30 20:42:19 Trace: [library/mobilesync] syncing listen later…
09/30 20:42:19 Error: [library/mobilesync] unexpected error: System.ArgumentNullException: Value cannot be null. (Parameter ‘source’)
at System.Linq.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument)
at System.Linq.Enumerable.Select[TSource,TResult](IEnumerable1 source, Func2 selector)
at Sooloos.Broker.Music.MobileSyncManager.SyncListenLaterItems(MobileSyncClientState clientstate, MobileSyncResponse response)
at Sooloos.Broker.Music.MobileSyncManager.Sync(MobileSyncRequest req)

[Daniele_Piancastelli (Dani)]

the latest build seems to have fixed the problem

[oleh (Oleh Ilash)]

Thanks for confirming!

[oleh (Oleh Ilash)]

Hey @gsuzor91, thank you for your efforts in investigating the core of the issue! This makes sense since the listen later feature is available only for the EA group. It won’t be actual anymore when it’s released to production.