mirror of
https://github.com/Rigellute/spotify-tui.git
synced 2026-04-26 16:15:55 +03:00
[GH-ISSUE #378] Exit code 101 #159
Labels
No labels
bug
enhancement
good first issue
help wanted
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-tui#159
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tom-doerr on GitHub (Apr 4, 2020).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/378
When I execute
sptit fails to start, although it used to work with version0.16.0I tested different versions but the error remains the same.Creating a new Client ID didn't help either.
Any ideas?
@Rigellute commented on GitHub (Apr 6, 2020):
Hmm... not sure.
Which OS are you using?
@tom-doerr commented on GitHub (Apr 6, 2020):
Linux Mint - it's based on Ubuntu 18.04.
I just remembered that it stopped working right after my computer ran out of storage, is it possible that spt tried to write to some file which resulted in that file becoming corrupted?
@Rigellute commented on GitHub (Apr 9, 2020):
That is possible yes! On every launch, authentication is performed and might attempt to persist the auth token to the file system. It's possible that this was the cause of your exit code.
@tom-doerr commented on GitHub (Apr 20, 2020):
Do you know where auth token is stored? I couldn't find anything on my file system.
@Rigellute commented on GitHub (Apr 21, 2020):
The auth tokens are persisted here
${HOME}/.config/spotify-tui/client.yml@tom-doerr commented on GitHub (May 2, 2020):
There were other files in that directory that seemed to be related to caching. After I deleted those and started spotify-tui, I was prompted to log into Spotify.
@Rigellute commented on GitHub (May 4, 2020):
Thanks @tom-doerr