Can't get Symfonium to sync with Astiga

App version

Production

Issue description

New install of Symfonium. Using Astiga as my media server. App is stuck at “Preparing sync” after 30 minutes. Usually only takes an app a minute to do initial sync.

Have tried compatibility mode based on old report with Astiga, but that did not help.

Turned on debug mode and exported log file to you under DMCR Music Library.

My Astiga interface is up and running and I can use it with other Subsonic apps.

Can you help?

Dennis

Device type

Phone

Media provider

Subsonic (Open)

Steps to reproduce

Connect to Astiga account. This seemed to work fine.
Then nothing more happens. Sync status remains at “Preparing sync”. Under the sync button there is another line that says “Unknown”.

I searched existing issues first

on

I understand that logs are mandatory

on

Log upload name / description

DMCR Music Library

Just found another data point: if I click on Files in the main menu, then on Subsonic, then on DMCR Music Library, the files all populate. I can drill down from the artist → album → songs.

So I clearly have a good connection with a running server. But none of the buttons that rely on metadata show anything.

Thanks will be fixed in next release, too large security for the Navidrome ID changes.

Thanks Tolriq.

Can you give me a sense when the next release will come out? Are we talking weeks or months?

Dennis

When it’s ready but less than month at least on the fdroid repo.

Just checking in @Tolriq but we now support, or should do, empty search3 queries… not sure if that changed anything.

Yes but

 {"subsonic-response":{"status":"ok","version":"1.16.0","serverVersion":"Astiga\/production"}}

Is not really OS :wink: You forget the type and openSubsonic there (subsonic-response | OpenSubsonic) that should be required for proper OS support.

Sure - we’ll add that. My understanding is that the empty query support is separate from and pre-dates OS though.

This issue have nothing to do with search3.

Apologies, I must’ve chosen the wrong thread to reply to. We’ll incorporate the OS fixes soon.