I know this is a duplicate of the previous report, but am filing separately as that issue is awaiting a response. I am using the new /config directory layout for local config and session_data storage (as seen in the included docker-compose and config file)
Describe the bug
The authentication information is not correctly stored in the keyring, according to the app
App was working fine before the recent updates. Love the app. So dearly want it to be working again!
Platform: Synology NAS
To Reproduce
delete all session data in ./config
docker-compose up -d
log in using following command (outside docker container):
I've also set the config to have logs at debug level. I don't see debug level logs. I know the config is somewhat working, as the Discord notifications about TFA requirements are working
I know this is a duplicate of the previous report, but am filing separately as that issue is awaiting a response. I am using the new /config directory layout for local config and session_data storage (as seen in the included docker-compose and config file)
Describe the bug The authentication information is not correctly stored in the keyring, according to the app
App was working fine before the recent updates. Love the app. So dearly want it to be working again!
Platform: Synology NAS
To Reproduce
docker-compose up -d
docker exec -it icloud /bin/sh -c "icloud --username=actualusername@mac.com --session-directory=/config/session_data"
Expected behavior keyring save should result in successful login
Configuration docker-compose.yaml
I've also set the config to have logs at debug level. I don't see debug level logs. I know the config is somewhat working, as the Discord notifications about TFA requirements are working
./config/config.yaml: