Albums showing twice, no songs in one of them
I recently connected Amperfy to Astiga. After syncing, all of my albums are showing twice in Amperfy. One of the albums has songs, one does not. I logged into Astiga with SubStreamer and every thing looks fine there, so I think the issue lies with Amperfy. Let me know what info you need to debug!
Empty albums remind me of this pull request: https://github.com/BLeeEZ/amperfy/pull/411. I think this fix is not yet in the Testflight version. Maybe you can see if anything changed when the Testflight version is updated or you can compile Amperfy by yourself.
Alright I'm on Testflight version 1.2.3 build 7 which I believe should include #411. Still seeing the double albums. 😞 How can I help further debug?
I guess we need to debug the response data send by the Astiga server. Do you happen to have a mac? Creating a customized build for you on macOS is way easier than doing the same on iOS.
My current hypothesis is that Astiga assumes isDir = true, if the flag is not set by the server. That is the relevant code snippet from the Astiga Android client.
if(get("isDir") == null) {
entry.setDirectory(true);
}
However, Amperfy's default behaviour assumes isDir = false if the flag is not set to be compatible with LMS
. Maybe this change causes the duplicated albums. I'm not sure.
If @BLeeEZ has nothing against it, I would propose we fix this and all other similar errors, by ignoring every album that does not contain any song. After all, an album without songs doesn't make sense and usually no sane subsonic / ampache server lets you create such an album in the first place. That means, if we encounter an empty album it is most certainly a bug.
Yeah I have a Mac! Happy to do some testing on a custom build.
Hello, having the same issue with a Navidrome server.
I'm also experiencing a similar issue with Amperfy through Navidrome where albums that have had their metadata updated (specifically in my case, singles that had no "album name" attached) show up as empty duplicates after their metadata has been fixed. The correct versions also show up as expected.