[GH-ISSUE #97] [Bug Report] Duplicate credentials file #83

New issue

Closed

opened 2026-02-27 04:57:26 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 04:57:26 +03:00

Owner

Originally created by @a0g83agbc84 on GitHub (Oct 8, 2025).
Original GitHub issue: https://github.com/Googolplexed0/zotify/issues/97

Originally assigned to: @Googolplexed0 on GitHub.

Zotify Version
v0.9.27

Bug Description
Credentials file stored in the same directory where zotify is executed from with terminal, even though the config specifies a location with a valid credentials file already.

Bug Triggering Command
Any command that requires auth.

Config File
Embeded config.json file here. Even better if its a config_DEBUG.json.

{
    "SAVE_CREDENTIALS": "True",
    "CREDENTIALS_LOCATION": "/config/zotify/",
    "OUTPUT": "{song_name} [{track_id}]",
    "SONG_ARCHIVE_LOCATION": "/config/zotify/",
    "ROOT_PATH": "/data/music/downloads/",
    "ROOT_PODCAST_PATH": "/data/music/downloads/",
    "SPLIT_ALBUM_DISCS": "False",
    "DOWNLOAD_LYRICS": "True",
    "MD_SAVE_GENRES": "True",
    "MD_ALLGENRES": "True",
    "MD_GENREDELIMITER": ",",
    "DOWNLOAD_FORMAT": "ogg",
    "DOWNLOAD_QUALITY": "very_high",
    "TRANSCODE_BITRATE": "auto",
    "SKIP_EXISTING": "True",
    "SKIP_PREVIOUSLY_DOWNLOADED": "True",
    "RETRY_ATTEMPTS": "1",
    "BULK_WAIT_TIME": "1",
    "CHUNK_SIZE": "20000",
    "DOWNLOAD_REAL_TIME": "True",
    "LANGUAGE": "en",
    "PRINT_SPLASH": "False",
    "PRINT_SKIPS": "False",
    "PRINT_DOWNLOAD_PROGRESS": "False",
    "PRINT_ERRORS": "True",
    "PRINT_DOWNLOADS": "True",
    "PRINT_API_ERRORS": "True",
    "PRINT_PROGRESS_INFO": "False",
    "PRINT_WARNINGS": "True",
    "TEMP_DOWNLOAD_DIR": "/data/music/downloads/tmp/"
}

I expect the credentials.json to remain only at CREDENTIALS_LOCATION, and not where zotify is executed from too.

Deleting the "current directory" credentials and executing again, only makes the file to be created again. Changing SAVE_CREDENTIALS to False does not fix the issue. Adding full path to CREDENTIALS_LOCATION makes zotify to complain that "a file already exists". A bit funny, that's the point :)

Thanks in advance for taking a look at this.

Originally created by @a0g83agbc84 on GitHub (Oct 8, 2025). Original GitHub issue: https://github.com/Googolplexed0/zotify/issues/97 Originally assigned to: @Googolplexed0 on GitHub. **Zotify Version** v0.9.27 **Bug Description** Credentials file stored in the same directory where zotify is executed from with terminal, even though the config specifies a location with a valid credentials file already. **Bug Triggering Command** Any command that requires auth. **Config File** Embeded `config.json` file here. Even better if its a `config_DEBUG.json`. ``` { "SAVE_CREDENTIALS": "True", "CREDENTIALS_LOCATION": "/config/zotify/", "OUTPUT": "{song_name} [{track_id}]", "SONG_ARCHIVE_LOCATION": "/config/zotify/", "ROOT_PATH": "/data/music/downloads/", "ROOT_PODCAST_PATH": "/data/music/downloads/", "SPLIT_ALBUM_DISCS": "False", "DOWNLOAD_LYRICS": "True", "MD_SAVE_GENRES": "True", "MD_ALLGENRES": "True", "MD_GENREDELIMITER": ",", "DOWNLOAD_FORMAT": "ogg", "DOWNLOAD_QUALITY": "very_high", "TRANSCODE_BITRATE": "auto", "SKIP_EXISTING": "True", "SKIP_PREVIOUSLY_DOWNLOADED": "True", "RETRY_ATTEMPTS": "1", "BULK_WAIT_TIME": "1", "CHUNK_SIZE": "20000", "DOWNLOAD_REAL_TIME": "True", "LANGUAGE": "en", "PRINT_SPLASH": "False", "PRINT_SKIPS": "False", "PRINT_DOWNLOAD_PROGRESS": "False", "PRINT_ERRORS": "True", "PRINT_DOWNLOADS": "True", "PRINT_API_ERRORS": "True", "PRINT_PROGRESS_INFO": "False", "PRINT_WARNINGS": "True", "TEMP_DOWNLOAD_DIR": "/data/music/downloads/tmp/" } ``` I expect the `credentials.json` to remain *only* at `CREDENTIALS_LOCATION`, and not where `zotify` is executed from too. Deleting the "current directory" credentials and executing again, only makes the file to be created again. Changing `SAVE_CREDENTIALS` to `False` does not fix the issue. Adding full path to `CREDENTIALS_LOCATION` makes zotify to complain that "a file already exists". A bit funny, that's the point :) Thanks in advance for taking a look at this.

kerem

2026-02-27 04:57:26 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-27 04:57:27 +03:00

Author

Owner

@Googolplexed0 commented on GitHub (Oct 9, 2025):

Changing SAVE_CREDENTIALS to False does not fix the issue. Adding full path to CREDENTIALS_LOCATION makes zotify to complain that "a file already exists". A bit funny, that's the point :)

Should be fixed on v0.9.28 and also in efficient-api. Let me know if it isn't.

I expect the credentials.json to remain only at CREDENTIALS_LOCATION, and not where zotify is executed from too.

The appearance of the cwd is strange. I think this was also the root cause with #87, since the previous behavior for the Session was to write to the default credentials location, which is cwd() / credentials.json.

@Googolplexed0 commented on GitHub (Oct 9, 2025): > Changing `SAVE_CREDENTIALS` to `False` does not fix the issue. Adding full path to `CREDENTIALS_LOCATION` makes zotify to complain that "a file already exists". A bit funny, that's the point :) Should be fixed on v0.9.28 and also in efficient-api. Let me know if it isn't. > I expect the `credentials.json` to remain _only_ at `CREDENTIALS_LOCATION`, and not where `zotify` is executed from too. The appearance of the cwd is strange. I think this was also the root cause with #87, since the previous behavior for the Session was to write to the default credentials location, which is `cwd() / credentials.json`.

kerem commented

2026-02-27 04:57:27 +03:00

Author

Owner

@a0g83agbc84 commented on GitHub (Oct 9, 2025):

Thank you again for the speedy fix, I'll check it out and let you know

@a0g83agbc84 commented on GitHub (Oct 9, 2025): Thank you again for the speedy fix, I'll check it out and let you know