-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
[BUG] Keyring never seen as saved - ERROR :: root :: sync.py :: 116 :: Password is not stored in keyring. Please save the password in keyring. #238
Comments
I'll add that subsequent attempts to authenticate do not prompt for password - just exits code 0. |
Try setting the ENV_ICLOUD_PASSWORD variable. |
Same issue. Adding the ENV_ICLOUD_PASSWORD variable to Docker container does nothing. 2024-07-05 21:07:58,417 :: INFO :: icloudpy.base :: base.py :: 253 :: Session file does not exist |
I have also tried the ENV_ICLOUD_PASSWORD variable. Still no luck |
Yep. Also still broken here. |
I was having the same issue and adding the |
Not for me. I am using that exact var. |
@rix1337 Onboarding is not smooth, I give you that. I've had to find my way to various trials and errors to get the latest version to run properly. The latest release(s) have made some underlying changes that are most likely the cause of the confusion. The other problem I am running into is this. Not a big deal, but it's not "clean." This never happened before the latest releases either. Are you seeing the same? |
Agreed. The docker was working for months. The recent changes broke it with the above error. |
Same issue here, keep getting the error "Password is not stored in keyring. Please save the password in keyring." on reboot. If I add the ENV variable ENV_ICLOUD_PASSWORD I get a TFA push notification from Apple on reboot. If I manually remove the password from keyring and login again everything seems fine in the console, but the errors are still there. |
I also noticed that the init script makes a directory called At this point, I am just shooting in the dark and hoping something sticks! 🙂 Let's wait for @mandarons to share guidance. |
Sounds like that’s the bug |
I debugged this project and found the issue. Do not run |
That worked, thank you! |
@mandarons the current docket build notifications reference a wrong dir |
Sorry folks for delayed response here. Life has been busy lately. I fixed 2 of the issues mentioned here (#245 and #246). It looks like documentation is also up to date with changes for using Please give it a try with |
@mandarons I updated yesterday to the last version. With this version I'll get the 2FA Apple prompt every hour. But I have already executed the command "docker exec -it icloud-docker /bin/sh -c "icloud --username=*** --session-directory=/app/session_data"" and filled in the Auth code once. Repeating that commend does not show any missing info, so I'll get no output anymore. So this is unfortunately still not working! :( This is the log:
|
@nicx : Please use |
@mandarons shit, that was my mistake. thanks for your hint! I just used the old command from an old mail :) |
I got a chance to try the latest "main" tag today, seeing this error:
|
@TheCase please try again. I added the missing file. It seems to be working on my system. |
Ok. That worked... But only when ENV_ICLOUD_PASSWORD is defined. This was not a requirement before the latest changes (where you moved config assets from /app to /config). I would prefer not to hard core my iCloud password in a file or provide it to the docker environment (where it is visible in the Unfortunately, this is still a bug. Auth was working fine without the var, previously. That said, I have a feeling you do this in your free time. I very much appreciate the effort you made to get this app working for several of us! |
@TheCase: Completely agree with you about recent hard requirement of ENV_ICLOUD_PASSWORD. Please try the following steps and let me know if that works (it seem to be working for me).
Please let me know if it works. I will update the documentation accordingly. |
Indeed, that --user add was the trick! Please note that this did not work until I deleted any existing session data from the /config volume. Thank you! This is perfect. Cheers! |
I will update the docs to indicate |
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 [email protected] --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:
The text was updated successfully, but these errors were encountered: