Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.spa files not migrated properly to new Backup location #3294

Closed
2 tasks done
chronobandit opened this issue Feb 5, 2025 · 2 comments
Closed
2 tasks done

.spa files not migrated properly to new Backup location #3294

chronobandit opened this issue Feb 5, 2025 · 2 comments
Labels
πŸ› bug Something isn't working

Comments

@chronobandit
Copy link

chronobandit commented Feb 5, 2025

πŸ” Have you checked Spicetify.app page for your issue?

  • I have checked the FAQ

πŸ” Is there already an issue for your problem?

  • I have checked older issues, open and closed

β„Ή Environment / Computer Info

- Spotify version: spotify-launcher 0.6.3-1
- Spicetify version: 2.38.9

πŸ“ Description

I believe the issue is caused by #3282

I was getting the message You haven't backed up and Spotify cannot be backed up at this state. Please re-install Spotify then run "spicetify backup apply".

Reinstalling spotify and spicetify didn't work for me, probably because the package manager doesn't fully delete things in the home folder because the spotify-launcher package doesn't own any files in home: pacman -Ql spotify-launcher.

This error happens when there are no .spa files in the Backup folder or the Apps folder. This happened because the .spa files were still in the old Backup location in .config/spicetify. Manually copying over the .spa files fixed the issue for me but I imagine this should have been done automatically and may cause others issues.

A migration should then also delete the old Backup and Extracted folder in .config/spicetify.

@chronobandit chronobandit added the πŸ› bug Something isn't working label Feb 5, 2025
@rxri
Copy link
Member

rxri commented Feb 5, 2025

There was no migration added and I'm aware of it. Not changing it back now. I may add the function that removes old files but not going to migrate these files since it already happened.

Image

@rxri rxri closed this as not planned Won't fix, can't repro, duplicate, stale Feb 5, 2025
@rxri
Copy link
Member

rxri commented Feb 5, 2025

I think it's resolved by 7f649da

@rxri rxri closed this as completed Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
πŸ› bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants