-
-
Notifications
You must be signed in to change notification settings - Fork 31.6k
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
iCloud integration stopped working (due to Apple SRP-6a implementation) #128830
Comments
Hey there @Quentame, @nzapponi, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) icloud documentation |
follow |
having this issue as well - following |
Same. Following. |
same here |
same |
A reminder to everyone that GitHub does have a "subscribe" feature you can use to follow this issue, and if you add a 👍 to the original post there'll be an easy count of people experiencing the same issue 😄 |
👍 Same issue |
stesso identico problema |
👍 |
welp |
Same Problem |
To avoid excessive notifications for everyone subscribed, please do not comment if you have the same issue. The owner is already informed. Instead, consider liking the original post and subscribing to updates. |
Same issue here. |
I too am having this issue. Whilst I know it is being worked on, is there a workaround as I have automations that rely on my Iphone and they do not currently work. |
👍 |
The problem is still present. |
Same problem. Reverting to 2024.10.1 did not fix it. |
Same issue |
This is a change in iCloud’s authentication method, so reverting wouldn’t fix this. The integration needs to be adjusted to be able to use apples new authentication mechanism. |
same here |
Same. Core version 2024.10.2 |
Same issue here -;( |
Check the fix for pyicloud at picklepete/pyicloud#456 for base.py |
Yes, that is what I followed, I will do it again and see what happens. |
Do we know when this will be included in the next home assistant release? |
Don‘t get that. |
I just Update to 2024.11.2, and password works again. |
Thanks! Did it… Working also …. |
The update works to a point, for me anyhow. It's now accepting my user name and app password, but I never get a iCloud verification code. What am I doing wrong? I have generated several different app passwords, but still no verification code. |
same here, only the iCloud PW worked for me (triggering the verification code), application passwords didn't work for me. |
I thought the whole point was once you had an application password that bypasses 2fa so you don’t need the verification code. |
Does someone know why the regular PW now works again with 11.2? Looks like something was broken and now works half-way (with regular PW and not app-PW). Of course, App-specific PW is the one that should work. |
Was it fixed in 2024.11.2? I tried to login with app password but that did not work. I was able to login with account password and 2FA. After i deleted the integration again and tried app password a second time it was accepted and the integration start working again. It would have been nice if there had been a line in the bug fix list. |
If you are using an app password 2FA code verification is not needed and you should not be asked for it. Only for using the account password you need the 2FA Code. And as you can see above app password worked for me. |
I tried app specific PW first, but it didn't work, there was an error shown. |
Regular password worked for me and it triggered giving me the code to enter. Will find out soon if I get prompted way to often. I don't mind every 30 days, but hopefully this can get sorted out. |
Did you try the way I managed to get app password working? |
not, didn't read the full post ;-) |
The app password does ask for a verification code just like the account password. I’ve got it working with the account password, but not the app password. |
Same here. Yes, I'm using application specific password... Logs are reporting: Logger: homeassistant.components.icloud.config_flow Error logging into iCloud service: ('Invalid authentication token.', PyiCloudAPIResponseException('Missing apple_id field')) |
Here an updated custom install, this includes changes pending merge in PyCloud. |
not working for me... even the normal icloud doesnt work... I arrived to the page of the 6digit code but i never receive it... same issue to anyone? |
I have the same issue I can provide a App Specific Password then it asks for a code put Apple is authenticating by sending a popup on my devices (did you initiate this login?) with just a yes or wasnt me response (no code) I select this but cant proceed any further I am assuming the integration needs to support alternative mfa techniques apple are using. |
Please note App Specific Password are not supported |
I'm using the latest ZIP file and unfortunately, I can't get it to work. It throws the following error when I try to add the integration:
|
|
still no working in latest HA update |
Will there come a future update that provides app specific password again? It worked before but stopped working againb after last update to 2024.12. |
any updates? |
The problem
The iCloud integration fix recently merged to support App Passwords relies on a one-time login with the 'regular' password and MFA prompt. However, Apple has updated their side and now require Secure Remote Password protocol which is currently not supported by
PyiCloud
. As a result the iCloud integration no longer works.BTW, it is already reported in the PyiCloud repo.
I opened this issue because the App Password issue was closed when the mentioned fix was merged.
What version of Home Assistant Core has the issue?
core-2024.10.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
iCloud
Link to integration documentation on our website
https://www.home-assistant.io/integrations/icloud
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: