Spotifywebapipython

Latest version: v1.0.194

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

Scan your dependencies

Page 23 of 33

1.0.62

* Updated `SpotifyDiscovery.DiscoverDevices` method to properly free Zeroconf resources after service discovery, and prevent possible memory leaks and crashes due to running out of resources.

1.0.61

* Added `ZeroconfGetInfo.IsInDeviceList` property that returns the status of active device list verification process (Verification not Performed, Verified Active, Verified Inactive).

1.0.60

* Updated `ZeroconfConnect` class to process all responses as JSON responses. It was found that some Spotify Zeroconf API capable devices were not properly setting the `Content-Type` in the returned http response header.
* Updated `SpotifyDiscovery` class to process the individual Spotify Connect instance names that were discovered via Zeroconf. Prior logic was adding a device for every IPV4 address that was found for an instance, assuming that each instance only contained one IP address; some services contain multiple IP addressess for the same instance name (specifically, the `SpotifyConnect` add-on, which runs in a docker container).
* Updated `SpotifyDiscovery` class to rename the `HostIpv4Address` property (and method arguments) to `HostIpAddress`. The address specified in this argument can be an IP address (e.g. "192.168.1.81") or an alias (e.g. "bose.speaker.kitchen").
* Updated `ZeroconfConnect` class to rename the `HostIpv4Address` property (and method arguments) to `HostIpAddress`. The address specified in this argument can be an IP address (e.g. "192.168.1.81") or an alias (e.g. "bose.speaker.kitchen").
* Updated various `SpotifyClient` methods to utilize the default `HostIpAddress` (or `Server` value if default `HostIpAddress` was not discovered) when connecting to a Spotify Connect capable device. Methods updated were: `PlayerActivateDevices`, `GetSpotifyConnectDevices`, `PlayerResolveDeviceId`.

1.0.59

* Updated `SpotifyClient` methods that call `PlayerResolveDeviceId` with a new parameter that indicates if the device should be resolved (true) or not (False). This allows multiple methods that call `PlayerResolveDeviceId` to be called from the same method, and only resolve the device one time. This was sone to ensure that device resolution did not occur more than once, as it's such a time consuming operation. Methods updated were: `PlayerMediaPlayContext`, `PlayerMediaPlayTrackFavorites`, `PlayerMediaPlayTracks`, `PlayerTransferPlayback`.

1.0.58

* Updated `SpotifyClient.PlayerResolveDeviceId` method callers to log a warning message if the specified device value could not be resolved and just return a null value.

1.0.57

* Updated `SpotifyClient.PlayerResolveDeviceId` method callers to gracefully handle the `SpotifyApiError` error if the specified device value could not be resolved.

Page 23 of 33

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.