Connecting to Google Drive

[Maik Qualmann]

Google has disabled our API key several times recently due to alleged 
violations of their policies. You don't get any exact information, it could be 
because users have downloaded too many images from Google Photos. There are 
also guidelines that the keys cannot simply be visible in public github/gitlab 
repositories.
Maybe our API keys have already been misused by other projects, we don't know 
for sure. We have therefore generated new API keys and they are only included 
in digiKam-8.3.0.

Maik

Am Mittwoch, 10. April 2024, 18:55:55 CEST schrieben Sie:
> Hi Maik -
> 
> Thanks for getting back to me.
> 
>  > The Google Photos/Drive tool only works from digiKam-8.3.0.
> 
> I find that hard to believe - as I have been using it successfully for
> several years before my hard drive failure.
> I don't recall what version of Digikam I was using then - but since
> 8.3.0 came out on 17th March this year, I doubt it was that one?
> 
> Steve
> 
> On 10/04/2024 17:48, Maik Qualmann wrote:
> > The Google Photos/Drive tool only works from digiKam-8.3.0.
> > 
> > Maik
> > 
> > Am Mittwoch, 10. April 2024, 18:32:56 CEST schrieb Steve Vaughan:
> >> Hi there -
> >> 
> >> I recently had a hard drive failure, and needed to re-install Linux and
> >> restore all my files.
> >> 
> >> Restoration of Digikam worked well, it accesses my existing database and
> >> I could carry on as before. Great.
> >> 
> >> Until it came time to upload some photos to Google Drive. I was taken
> >> through the procedure of re-authentication with Google.
> >> 
> >> That's not working.
> >> 
> >> I'm using Digikam v7.5.0 on Linux Mint. I use Firefox as Web browser.
> >> 
> >> I select Tools->Export to Google Drive
> >> 
> >> Firefox launches automatically and I get to choose my required Google
> >> account.
> >> 
> >> Then I get the "Digikam wants to access your Google Account" screen and
> >> I click "Allow"
> >> 
> >> Then Firefox is redirected to a URL like this :
> >> http://127.0.0.1:8000/?state=07ad2189a2294363bd63e87ed0531003&code=4/0Aea
> >> YSH BK6qozU6sicyg2TfbJ9Z1jVD3R6Lg etc etc etc
> >> 
> >> and that's as far as we get. It hangs there.
> >> 
> >> Has google changed the way it authenticates?
> >> 
> >> Regards
> >> 
> >> Steve Vaughan