Difegue / Stylophone

A pretty cool™️ MPD client in .NET. Based on MpcNET.
https://tvc-16.science/stylophone-27.html
MIT License
135 stars 10 forks source link

Sending ListPlaylistInfoCommand failed: An item with the same key has already been added #16

Closed xBelladonna closed 3 years ago

xBelladonna commented 3 years ago

First of all, thank you for identifying and fixing the issue in #14 so quickly! I've downloaded the update and it seems the problem was fixed, though there is another issue preventing the display of the playlist contents itself. I seem to be getting a couple different error messages, as below: image image

The queue is also blank and does not show the contents, though nothing causes a crash this time. The play/volume controls are working as expected and do play what's in the queue despite not showing it. I don't know much about Windows applications and I'm not sure how you obtained the stack trace last time but would you know how I could retrieve and supply useful debugging data from the Store app?

Difegue commented 3 years ago

Well, you were lucky that #14 was easy to identify and that I could reproduce it 😁
I got the stack trace from the anonymized Windows telemetry reports, but those are only sent on hard crashes.
The store version is basically impossible to debug most of the time since it's all compiled to native code on submission, sadly.

However, this is an error obtained while parsing results from an MPD command, so in a way it's much easier to debug! 😀
I'm guessing from afar that this is a bug in the way I'm transforming results from the listplaylistinfo command into a list of tracks.

I'd like to have the raw command output from your server so I can see what's wrong:
You can get it using another client library, the python one seems to be the easiest to setup:
image

I should add some form of Debug view to the app so that one can see the raw MPD requests/responses as they come, but for the time being that's all I got. 😓

Difegue commented 3 years ago

I've pushed a fix that should mitigate this problem in the next release.