Scoop-Spotify issues

Spicetify-cli: Some scripts are not recognised as cmdlet, scripts, ...

5

When I first installed and later updated this bucket through scoop, I got this error message: ```yml The term: init-spicetify-config-and-apply.ps1 is not recognized as a name of a cmdlet, function,...

jacob-thanh

Spotify doesn't work with BlockTheSpot

4

```shell scoop install spotify-latest scoop install blockthespot ``` However, it does work when I install spotify manually (through the exe) and apply BlockTheSpot manually.

rollingmoai

Extensions missing

2

i recently installed spicetify, but whenever i try to add a new theme it says error Extension "newRelease.js" not found. error Extension "queueAll.js" not found. then, when I open the...

tbweet

Fix init-spicetify-config script for spicetify v2

4

* Fix config file name * Remove missing extensions Merging this will fix #54

SaifAqqad

Update the config init script to handle both the profiles

1

Now that we have 2 versions of the config script, for backwards compatibility sake, we should check for both and only add the extensions and stuff when we need to,...

Lunchb0ne

remove old deprecated extensions from script

1

These two no longer exist in the repo and are giving errors every time `spicetify apply` is run. ```powershell spicetify-apply.cmd spicetify v2.7.1 .... .... Transferring extensions: error Extension "newRelease.js" not...

mockuser404

Spotify's built-in updater is not disabled

4

Maybe the cause which leads to #34. According to the Readme: > Spotify's built-in updater is disabled, and Scoop should be used to update it instead. But I am asked...

dionysius

[email protected]: Hash check failed

1

Hash check failed! App: spotify/spotify-latest URL: https://download.scdn.co/SpotifyFullSetup.exe First bytes: 77 90 144 0 3 0 0 0 Expected: ee24bce5c0a2f1686e4eaac6886e7afee5842fb920572056ed822ee8dadd5d0b Actual: e40bf92a02b7f3f3d460192ffd627d076e4a07c05dc277ccea63ed4df6c5c3fc

hozansahin