Hangs at page 637 on Waterfox and Chrome

[SwooshyCueb]

I only tried my own account (SwooshyCueb) but it always stops after page 637.

[benfoxall]

Oh, interesting it looks like there's a response error in page 637

Seems to be this listen

<name>é6��/8</name>

https://www.last.fm/music/%C3%A96/_/%C3%83%C2%A96%03%10%2F8

🤔 I'm not too sure what to do about this. Could skip the page on an error which would lose some tracks but let you continue on with downloading the rest of your tracks

[VeXHarbinger]

I got one error and was able to save. See the [Other Thread](#25) on the same topic if it's not in this one. "For we are the music makers, and we are the dreamers of dreams" - Willy Wonka

[SwooshyCueb]

I deleted the scrobble in question, and it was able to finish without errors.

[Lemodile]

Having the same issue (at page 151). But I can't figure out which scrobble is causing it.

Any tips? Or is there a list of characters that would not work with this method? Thanks in advance!

[VeXHarbinger]

Actually, the error/Issue is pretty clear;

So you have a character not allowed by the XML's DTD. So you either have to delete that track from your Last.FM Lib, rename it to be a character allowed by the DTD (So mostly basic characters).

Since this Character is in conflict with the XML/RSS's DTD it will always throw an error when it attempts to validate the XML data because of that character.
Since we can all still download our files, I'd say the issue is purely cosmetic and TBH of our own creation. We just need to name tracks appropriately or rally for the DTD to be expanded.
Course that is just my opinion and it's not my code.

[Lemodile]

Thanks for looking into it. Probably a good thing to know: I'm not all that technical, but enjoy music a whole lot.

So for others like me these are the steps that slowly but surely are getting me through this:

• open console when fetching your scrobbles (by pressing f12).
• if any error appears it should mention a url that ends with a page number.
• open that page in a web browser that shows you the file up to the error (firefox doesn't do that for me but edge does), that way you can identify the track that's causing the issue.
• find that track on last.fm. If you, like me, listened to that track many times, know that last.fm can delete them all at once
• repeat process and hope it doesn't get stuck on another track. So far I've had to delete 8 different tracks and I'm at page 187/700ish