<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Issues with the /me/following/ Web API endpoint in Spotify for Developers</title>
    <link>https://community.spotify.com/t5/Spotify-for-Developers/Issues-with-the-me-following-Web-API-endpoint/m-p/5518643#M8275</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since last Friday (3rd March) I've been experiencing the following issues with the endpoint to get a user's followed artists:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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&amp;nbsp;&lt;/P&gt;&lt;P&gt;7zwVV1dEwZ9D8tyyBQpZHc which was returned on the 2nd paged request (see attached file).&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Presumably these issues are related. If someone could look into it for me please that would be much appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Dave&lt;/P&gt;</description>
    <pubDate>Fri, 10 Mar 2023 13:13:03 GMT</pubDate>
    <dc:creator>dm_u</dc:creator>
    <dc:date>2023-03-10T13:13:03Z</dc:date>
    <item>
      <title>Issues with the /me/following/ Web API endpoint</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/Issues-with-the-me-following-Web-API-endpoint/m-p/5518643#M8275</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since last Friday (3rd March) I've been experiencing the following issues with the endpoint to get a user's followed artists:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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&amp;nbsp;&lt;/P&gt;&lt;P&gt;7zwVV1dEwZ9D8tyyBQpZHc which was returned on the 2nd paged request (see attached file).&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Presumably these issues are related. If someone could look into it for me please that would be much appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Dave&lt;/P&gt;</description>
      <pubDate>Fri, 10 Mar 2023 13:13:03 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/Issues-with-the-me-following-Web-API-endpoint/m-p/5518643#M8275</guid>
      <dc:creator>dm_u</dc:creator>
      <dc:date>2023-03-10T13:13:03Z</dc:date>
    </item>
    <item>
      <title>Re: Issues with the /me/following/ Web API endpoint</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/Issues-with-the-me-following-Web-API-endpoint/m-p/5518817#M8278</link>
      <description>&lt;P&gt;They must be making changes to the follower endpoints right now, I reported a related bug around that same time that they haven't gotten around to fixing yet.&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.spotify.com/t5/Spotify-for-Developers/New-Bug-Top-Artists-follower-count-is-broken/m-p/5514217#M8176" target="_blank"&gt;https://community.spotify.com/t5/Spotify-for-Developers/New-Bug-Top-Artists-follower-count-is-broken/m-p/5514217#M8176&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Mar 2023 20:41:09 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/Issues-with-the-me-following-Web-API-endpoint/m-p/5518817#M8278</guid>
      <dc:creator>Murk404</dc:creator>
      <dc:date>2023-03-10T20:41:09Z</dc:date>
    </item>
    <item>
      <title>Re: Issues with the /me/following/ Web API endpoint</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/Issues-with-the-me-following-Web-API-endpoint/m-p/5519782#M8303</link>
      <description>&lt;P&gt;I see, thanks for the follow up. Hopefully they can resolve soon.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Mar 2023 12:23:14 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/Issues-with-the-me-following-Web-API-endpoint/m-p/5519782#M8303</guid>
      <dc:creator>dm_u</dc:creator>
      <dc:date>2023-03-13T12:23:14Z</dc:date>
    </item>
  </channel>
</rss>

