Spotifywebapipython

Latest version: v1.0.194

Safety actively analyzes 723144 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 22 of 33

1.0.68

* Updated `ZeroconfConnect._CheckResponseForErrors` method to not process the Spotify Zeroconf API response, as each method calling the check response method will process the returned status.

1.0.67

* Updated `SpotifyClient.IsDeviceId` class to recognize UUID-formatted device id's (e.g. "48b677ca-ef9b-516f-b702-93bf2e8c67ba").
* Updated `ZeroconfConnect` class to not default the `version` value to `1.0`, in the event that newer devices may not support that version identifier.
* Updated `ZeroconfConnect.Connect` method to not pass the `loginId` parameter to the request.
* Updated `ZeroconfConnect.Connect` method to issue a Disconnect to reset the user context if the public key value is "INVALID".

1.0.66

* Updated `ZeroconfResponse` class to convert the `status` and `spotifyError` values to numeric from string. Some Spotify Connect devices return them as strings, while other return them as numerics.

1.0.65

* Updated `ZeroconfConnect.Connect` method to account for "ERROR-INVALID-PUBLICKEY" statuses returned for some devices. This will retry the connection request with the PublicKey value returned from the initial request.

1.0.64

* Updated `SpotifyClient.GetSpotifyConnectDevices` method to correctly set the currently active device.

1.0.63

* Updated `ZeroconfConnect` class to process the Spotify Zeroconf API status code from the JSON response instead of processing the HTTP request status code. It has been found that some Spotify Connect manufacturers return different HTTP status codes than other manufacturers; but the Spotify Connect `status`, `statusString` and `spotifyError` JSON properties seem to be consistent across the board.
* Updated `SpotifyClient.GetSpotifyConnectDevices` method to filter out duplicate Spotify Connect Device entries for devices that have been grouped together. For example, the "Bose-ST10-1" and "Bose-ST10-2" are grouped as a stereo pair; there will be two Zeroconf discovery result entries with different instance names, but their Zeroconf getInfo endpoint url will be the same. When this happens, it causes the values to show up as duplicates if we process both of them.

Page 22 of 33

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.