adrianhajdin/project_music_player

Top Play component is unable to fetch artist details in line no 112

Closed this issue · 6 comments

shivam-jha2712 commented

Please help us with that as the error is coming in line number 112 (in your code) In my code it is 117.
Screenshot (166)

weichi2002 commented

I figured it out. It's not because there are any issues with the code, but rather the API is prolly up to its limit. Only 500 songs per month hard limits. Also nice github portfolio.

stevensps commented

I figured it out. It's not because there are any issues with the code, but rather the API is prolly up to its limit. Only 500 songs per month hard limits. Also nice github portfolio.

I don't believe this is the issue. I am experiencing the same issue as in the screenshot above and just checked my RapidAPI analytics dashboard. I have only made 101 API calls in the last 30 days. Still looking for a solution.

image
image

stevensps commented

I figured it out. By console logging the topPlays array, I was able to see that ShazamAPI modified their structure. So, to fix the topPlays error you need to do the following steps. I really hope this helps! I'm still testing but am at least able to get my page back to play songs.

  1. Update base URL and sub endpoint queries in ShazamCoreAPI
    image

  2. Navigate to topPlays and console log the topPlays array. If you notice in the screenshot below, another "0" is now added to the array structure.
    image

  3. This causes the need to update the code in the screenshot below, and anywhere else with this code structure in TopPlays. Keep refreshing the page and the console log will tell you the lines that you need to update.
    image

weichi2002 commented

@TallestStatue23 Thank you. I tried your method and it worked for a little while. But now I am getting this

image

Do you know what this might be. Thank you very much.

shivam-jha2712 commented

I figured it out. It's not because there are any issues with the code, but rather the API is prolly up to its limit. Only 500 songs per month hard limits. Also nice github portfolio.

Thanks for the Appreciation 😁. And yes the solution proposed by @TallestStatue23 does work.

shivam-jha2712 commented

I figured it out. By console logging the topPlays array, I was able to see that ShazamAPI modified their structure. So, to fix the topPlays error you need to do the following steps. I really hope this helps! I'm still testing but am at least able to get my page back to play songs.

  1. Update base URL and sub endpoint queries in ShazamCoreAPI
    image
  2. Navigate to topPlays and console log the topPlays array. If you notice in the screenshot below, another "0" is now added to the array structure.
    image
  3. This causes the need to update the code in the screenshot below, and anywhere else with this code structure in TopPlays. Keep refreshing the page and the console log will tell you the lines that you need to update.
    image

Thanks this helps to save the trouble and thanks for the solution