You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have read the README, the theme is installed/configured correctly and the "Troubleshooting" section contains no information related to my problem
Do you have the latest versions of Spicetify, Spotify and Bloom?
I'm using the latest versions of Spicetify, Spotify and Bloom
Is there already an issue for your problem?
I have checked older issues, open and closed
Is your problem definitely caused by the theme?
I have checked the app behavior without the theme and it is different
Environment & Computer Info
- Spotify version: for Windows 1.2.11.916.geb595a67
- Installed from: Spotify site
- Spicetify version: v2.18.1
- Color scheme: darkmono
- Extensions: fullAlbumDate.js, adblock.js, spotifyGenres.js, volumePercentageWrapper.js, fullScreenWrapper.js, copytoclipboard2.js
- Custom apps: marketplace, lyrics-plus
- Bloom installation method: PowerShell script
Description
Right-click on any folder
Press "Choose folder image"
Choose any image and submit
That's it. The image does not appear. However, if you disable the LibraryX view in the Spicetify experimental features menu and reload the app, it will display. This is probably related to a different playlists list mapping in LibraryX view.
Screenshots
LibraryX:
Classic:
The text was updated successfully, but these errors were encountered:
Did you read the README?
Do you have the latest versions of Spicetify, Spotify and Bloom?
Is there already an issue for your problem?
Is your problem definitely caused by the theme?
Environment & Computer Info
Description
That's it. The image does not appear. However, if you disable the LibraryX view in the Spicetify experimental features menu and reload the app, it will display. This is probably related to a different playlists list mapping in LibraryX view.
Screenshots
LibraryX:
Classic:
The text was updated successfully, but these errors were encountered: