Open SnakerBone opened 4 years ago
Giving this a nudge since it's still an issue when you follow the instructions and pull your own API key and put into the userConfig file or directly into the app itself : you still get the rate error.
which version of the app are you using?
Current RC 7.0.1
Might also be likely the api key didn't get updated if it's still returning an error for the new api key.
You can open devtools with Control + Shift + I
(Or Command
on mac), go to the network tab & then confirm whether the client_id param in the get request has changed; (eg/ Mine would be URL:https://api.soundcloud.com/tracks/737929528/stream?client_id={id}
)
I can investigate further tomorrow to get a better idea, but currently there is not too much we can do about the root cause of the api key having really dumb limits.
small update; Haven't had much time to work on any soundnode stuff in the past 3 days, been mostly preoccupied with personal things.
Should be able to have time to check if the userConfig is bugged in the next couple of days, otherwise anything to do with any api keys is way beyond what I am able to fix (as that'd be an issue with soundcloud not us)
I have been able to get around it with the youtube-dl patch: https://github.com/Soundnode/soundnode-app/pull/1029
Soundcloud API Request limit when I try to play a song,,