Network error by querying some artists
I'm having the issue on the Android app.
Steps to reproduce the issue:
1. Select "Alphabetically" in the Artist lists section
2. Select one artist
3. A network error occured and no luck with retries
I'm not sure what makes the error, the following is some example artists which work well and don't work.
👍: 80kidz, A-bee, 17 Pictures
👎: Aldo Ciccolini, Alexander Ivashkin
I thought " " in a name caused the error, but it doesn't seem to be the case.
Post edited by tpy on
Comments
Thanks, we'll review this today.
We've worked out the cause - it relates to albums with multiple different artists for different tracks. In some cases we aren't resolving these as "Various Artists". We're looking into the best fix.
This should now be fixed.
I still have the same issue. Maybe new version hasn't rolled out to me yet?
Will try again later.
Have you refreshed the list? I did find an extra issue where a subset of tracks are returned (not a "Network error") but I'll retest this later.
Yeah I have restarted the app and refreshed the artists "Alphabetically" list, but still having the network error.
Thanks for confirming - I'll check this today.
Confirmed it's still an issue. Sorry about that, will look into.
Happy new year!
Any updates on this issue? This is still blocking my kind of daily use.
If at least a root cause is identified, I could update problematic metadata on my end.
Yeah - really sorry. We're coming to the end of testing some fixes and we'll deploy them soon.
The problem relates to the use (or lack of) the
band
field (ALBUM ARTIST
) and how we identify albums. You may find better luck if you fill that in, but it's probably better to wait a couple of days for a release (maybe early next week).Thank you for working on this!
I admit that my use of Album and Album Artist is not so common as I use Album for each classical music piece (so bunch of artists per album).
I will wait for the release. I m supposed to already fill out both fields for all files tho.
Thanks 👍️ obviously, either way you shouldn't be getting errors.
We've deployed some changes which, we hope, should fix the issue. A forced re-sync is required, but I can perform a separate data update if you'd rather. Let me know if you want me to do that.
Thanks! I will kick force resync off.
Thanks - let us know how it goes.
There might still be a little more data manipulation needed btw (automated fix coming for that) so if it still seems wrong let me know.
Got it.
A bit off topic but when we get the following message,
Your previous sync is still running. Please wait for your previous sync to finish before starting a new one. The progress of your previous sync is shown below.
Has the next sync task been already queued? Or should I revisit the page later to run the sync?
Because of this, I couldn't run a new sync so far.
It would be great if you could make sure that my DB is in good shape.
Hi @tpy - I think your automated sync was running before, already.
I stopped that (another one had restarted since) and I'm currently working on the data, so things might look a little screwy over the next hour or two.
@tpy That should be done now. Can you test and report any anomalies?
It s working now!
Thanks for addressing the issue!
👍️