Telegram remote actions not working about docker-icloudpd HOT 5 CLOSED

I've actually had a look at this tonight and found that it is in better shape than I thought it was. I attempted a remote re-authentication and it worked first time when sending the MFA code to both a trusted SMS number, and also using the code generated by the built in Apple MFA.

I did uncover a bug which I've highlighted, and have made some further modifications to improve the re-authentication workflow. It's worth pointing out however, that it's only possible to use remote reauthentication feature if the current cookie is valid. If it expires, the container stops polling Telegram, so needs local reauthentication.

It also seems that cookie expiry notifications are not being sent, as one of my containers failed today, but I have not received any notifications whatsoever.

from docker-icloudpd.

Can you set debug_logging=true in your icloupd.conf file and restart the container.

Authentication is broken at the moment. An upstream change altered the console output and I've not had a big enough chunk of time to look into it yet.

from docker-icloudpd.

Hello, thank you for your answer ! Forced synchronisation is now working, no success with reauth so far.

from docker-icloudpd.

I have a similar problem, if I send the command nothing happens. This is the debug log:

2024-08-17 15:26:52 INFO     Monitoring Telegram for remote commands prefix: chris
2024-08-17 15:26:52 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:27:52 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:28:52 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:29:52 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:30:53 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:31:53 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:32:53 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:33:53 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:34:53 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:35:54 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:36:54 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:37:54 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:38:54 DEBUG    Polling Telegram for updates newer than: 30547590

from docker-icloudpd.

I have a similar problem, if I send the command nothing happens. This is the debug log:

2024-08-17 15:26:52 INFO     Monitoring Telegram for remote commands prefix: chris
2024-08-17 15:26:52 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:27:52 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:28:52 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:29:52 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:30:53 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:31:53 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:32:53 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:33:53 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:34:53 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:35:54 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:36:54 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:37:54 DEBUG    Polling Telegram for updates newer than: 30547590
2024-08-17 15:38:54 DEBUG    Polling Telegram for updates newer than: 30547590

That can't be monitoring the same bot as what you are sending messages to... When it finds an update it will process like this:

2024-08-23 15:06:52 DEBUG    Polling Telegram for updates newer than: 231091824
2024-08-23 15:07:52 DEBUG    Polling Telegram for updates newer than: 231091824
2024-08-23 15:07:52 DEBUG    Updates to process: 1
2024-08-23 15:07:52 DEBUG    Processing update: 231091825
2024-08-23 15:07:52 DEBUG    New message received: NotMe
2024-08-23 15:07:52 DEBUG    Ignoring message: NotMe

This script is me sending bogus data to the bot. The script sees the message, but ignores it because it's not for that user. I have 5 containers with different Apple IDs monitoring the same bot chat.

I'm closing this off though as OP's issue is resolved. If you're still having issues, please raise new issue once you've checked the stuff above.

from docker-icloudpd.