Cannot set playlist public to private or change the setting

[barryCan]

Plan

Premium

Country

Canada

Device

mac Studio

Operating System

macOS

Using the API I can no longer create private playlists. All created playlists are public regardless of the supplied value.  Nor can I change the existing public value.  I'm using Authorization Code Flow with the following scopes set: 

playlist-read-private playlist-modify-private playlist-modify-public

On the Spotify documentation web pages if I try to create a new playlist or change the details, everything works except setting public to false.

ANy help would be appreciated.

[barryCan]

This must have been a server side issue as all code and Spotify Documentation pages just started working.

It's a little strange as it hasn't worked for close to a day.

[Ximzend]

You can read about this under "Public, Private, and Collaborative Status" here: https://developer.spotify.com/documentation/web-api/concepts/playlists

[barryCan]

I have all the required scopes.

I've found that the public member returned by the Get User's Playlists call are sometimes incorrect.  They do not reflect the public status of the playlist as displayed in the desktop application.  Additionally the modification of the public member is hit and usually miss when changing it in a Change Playlist Details call.  These issues appear in my code and in the Spotify console.

[Ximzend]

The API returns "public":true when a playlist is publicly displayed at someone's profile. In other cases, it will return "public":false.

[barryCan]

Actually this is not happening.   Get User's Playlists is returning a different 'public' value than Get Playlist for the same playlist.  Further, Change Playlist Details is not returning an error, however, all changes take place except the 'public' modification.

[Lugico]

Got the exact same issue here. Playlists can be made public (aka. displayed on the profile) but can never be set back to private (aka. hidden from the profile) using the Web API

I've described it in more detail on this post.