Skip to content
This repository has been archived by the owner on Mar 24, 2024. It is now read-only.

Cannot use app specific password in docker? #29

Open
liquidtoon01 opened this issue Oct 13, 2021 · 2 comments
Open

Cannot use app specific password in docker? #29

liquidtoon01 opened this issue Oct 13, 2021 · 2 comments
Labels
upstream bug Something should be fixed in an upstream dependency

Comments

@liquidtoon01
Copy link

liquidtoon01 commented Oct 13, 2021

Hi, I'm trying to use an app specific password to negate the need for MFA, but i am getting the following error;

CRITICAL:root:'dsInfo'
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/gimme_iphotos/__init__.py", line 81, in main
    DownloaderApp(vars(args)).run()
  File "/usr/local/lib/python3.9/site-packages/gimme_iphotos/downloader.py", line 106, in run
    api = self.connect_to_icloud(config)
  File "/usr/local/lib/python3.9/site-packages/gimme_iphotos/downloader.py", line 122, in connect_to_icloud
    api = PyiCloudService(config["username"], config["password"])
  File "/usr/local/lib/python3.9/site-packages/pyicloud/base.py", line 211, in __init__
    self.authenticate()
  File "/usr/local/lib/python3.9/site-packages/pyicloud/base.py", line 239, in authenticate
    self.params.update({"dsid": self.data["dsInfo"]["dsid"]})
KeyError: 'dsInfo'

Any ideas why this is happening? Happens when doing interactively or via config file

@deegs
Copy link

deegs commented Oct 15, 2021

FWIW I get the same error when using an app specific password with a pip3 install but this seems to be an upstream issue in pyicloud.

@Zebradil
Copy link
Owner

@liquidtoon01 Thank you for reporting this issue!

I think I had some issues with app-specific passwords and pycloud in the past when I was developing gimme-iphotos, but I can't find the corresponding issue currently.

@deegs Thanks for linking the upstream issue!

I haven't had time to dig into pycloud yet, but from the linked issue it seems like this can't be fixed easily. And it is definitely has to be fixed in the upstream, unfortunately.

I will keep this issue opened until we have a solution.

@Zebradil Zebradil assigned Zebradil and unassigned Zebradil Oct 15, 2021
@Zebradil Zebradil added the upstream bug Something should be fixed in an upstream dependency label Oct 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
upstream bug Something should be fixed in an upstream dependency
Projects
None yet
Development

No branches or pull requests

3 participants