Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[json.exception.type_error.304] cannot use at() with null #53

Open
meow6969 opened this issue Apr 3, 2021 · 2 comments
Open

[json.exception.type_error.304] cannot use at() with null #53

meow6969 opened this issue Apr 3, 2021 · 2 comments
Labels

Comments

@meow6969
Copy link

meow6969 commented Apr 3, 2021

when trying to load this playlist "https://open.spotify.com/playlist/52vsJpNfjXxTwMBptTb34w?si=cZ0EjtYKQ4eixPxVJxPo6A" I get an error saying The following error(s) occurred during loading of the location(s): [json.exception.type_error.304] cannot use at() with null
I have tried: reinstalling the component and tried loading the playlist on multiple computers.

@TheQwertiest
Copy link
Owner

Thanks, I'll take a look.

@liamharper2453
Copy link

liamharper2453 commented Jan 5, 2022

Just had this issue on my own playlist. I suspect the issue is related to null tracks appearing in JSON responses from Spotify's end. In OP's playlist, it says there are 288 songs. However, if you scroll to the bottom you can see in actuality there is only 283. My playlist with the same issue also has a miscount.

When calling the API against OP's playlist it returns 288 tracks. However, the missing 5 appear as the below in the JSON response:

{
"track" : null
}

If you make a new playlist by copying every song in OP's playlist the null tracks above aren't copied, the counts match and the issue does not present itself.

So, my recommended (non-programmatic) fix would be to copy all the songs in your playlist into a new one. This fixed my issue and suspect it will fix yours too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants