Type in your question below and we'll check to see what answers we can find...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Since last Friday (3rd March) I've been experiencing the following issues with the endpoint to get a user's followed artists:
1. The next and after paging cursor fields return null even though there are further artists to navigate. It appears to hit a certain artist as the final item in the artist array on one of the pages which then breaks the paging cursor - in one test I did, the artist with id
7zwVV1dEwZ9D8tyyBQpZHc which was returned on the 2nd paged request (see attached file).
Strangely this only seems to happen on some user accounts when the limit parameter is set to 50. By setting to 49 for example the cursors are fine and I can navigate through all of their artists without issues, though of course in the test mentioned above 49 avoids this artist as the final item and that artist is infact not present at all in the results.
2. On some user accounts the total followed artists also doesn't seem to match the number of artist items returned. Sometimes the total's just one more than the items returned, sometimes it's far lower than the number of items returned.
Presumably these issues are related. If someone could look into it for me please that would be much appreciated.