Fix: Handle Null JSON Body in Spotify API Response

[tmdeveloper007]

Description

Added try-catch around response.json() in services/spotify/api.ts.

Pillar

• Other (Bug fix, refactoring, docs)

Checklist

• I have read the CONTRIBUTING.md file.
• My commits follow the Conventional Commits format.

Note

Please assign this PR to the tmdeveloper007 account.

Closes #8684

[retenta-bot]

This pull request addresses the issue of handling null JSON bodies in the Spotify API response, which is crucial for maintaining the robustness of our application. Similar past decisions have focused on improving error handling in the Spotify integration, ensuring that we gracefully manage unexpected API responses. Thank you for your contribution, and please let me know if you need any further assistance!

[github-actions]

📦 Next.js Bundle Size Report (Gzipped Sizes)

✨ No significant bundle size changes detected.

📊 Summary of Totals

Category	PR Size	Base Size	Difference
Total JS	4939.27 KB	4939.27 KB	0 B
Total CSS	348.46 KB	348.46 KB	0 B

[Aamod007]

Good defensive programming! Wrapping the
esponse.json()\ call in a try-catch block inside \services/spotify/api.ts\ is exactly the right approach to gracefully handle cases where the Spotify API returns a 204 No Content or a malformed JSON response. It prevents unhandled promise rejections. Looks solid.