Spotify Access Token Fetch Error
I'm currently encountering an issue while using Moonlink.js with Spotify support. Here's the error log:

29 Replies
Since it's early morning where I live, I'll do a hotfix on this in about 8 hours.
Thanks for reporting
Thanks
It's endpoint got changed 🙃
Also the reason param in the url.
hey just wanted to know if this is fixed
sorry for the ping
@1Lucas1.apk
Just 3 hours passed
Okay
Thanks for the reply
@1Lucas1.apk https://github.com/Ecliptia/moonlink.js/commit/1e3594afc3d2c55605c0c5ce960c447862e58bcd
GitHub
fix: Spotify endpoint change · Ecliptia/moonlink.js@1e3594a
Signed-off-by: Emmanuel Lobo <76094069+UnschooledGamer@users.noreply.github.com>
Is it fixed ?
As per my testing yes. Lucas Will check & release
He should be here anytime in some hours
waiting for him :Basu_PandaEatingChips:
might have gotta held IRL works.
Yeah
you can install that version. But I can't ensure it might have everything as dev & main branch are not synced.
6 commits behind v4.
(v4 = current main branch)Nah, I'll wait until the release.
GG @INSANE17?.!!, you just advanced to level 1!
The internet cables broke in the street because of a tree now that they finished fixing them
Sorry for the delay
wait
Thanks for fixing it, you're awesome ✌🏽
don't publish
I forgot to change embed to web-player
I still need to remove these errors that cause these fatal errors, let it automatically disable when the source cannot obtain this necessary information.
hmm, just warning it.
with console.warn or process.warning
To publish, just put the version in package.json and a release on github
Sometimes there are people who don't like logs, so I think I'll send it through some event, I think through debug
you should warn to my guess. As else User will need to dig down. a process.warning or warn can be handled.
you can suppress them with a flag/option
Then I will send it through console.warn
I made an option to disable it and realized that it is not working. I will have to fix that too.
@1Lucas1.apk hey ! Good to see you !
Hey, so I'm still getting this error with the latest version, is it still an issue atm with moonlink? Or could it be my application.yml needs to be updated?
edit* not getting that error anymore sorry, but I'm getting:
TypeError: Body is unusable: Body has already been read
yeah, commenting Spotify out from the application.yml fixed it lol, spotify is working nowThis is because of fetch, I'll soon rewrite makeRequest to http
So does moonlink not need lavasrc? Seems to work fine with lavasrc Spotify configuration disabled
Since last month I introduced a dynamic sourceManager and added support for Spotify and Deezer natively, but it needs a default source to stream