*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY when I try to load list of albums during import the following popup is shown Error transferring https://photoslibrary.googleapis.com/v1/albums?pageSize=50 - server replied: (note there is no further text after the ":" sign) STEPS TO REPRODUCE 1. try to impor the google photos 2. login to google account succesful 3. list albums OBSERVED RESULT error msg EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION also Export having the same issue
Our API key has been blocked again by Google - I'm fed up... See these stories: Bug 472494 Maik
Can confirm that the same issue is occurring on Digikam 8.3.0 on MacOS.
*** Bug 491314 has been marked as a duplicate of this bug. ***
*** Bug 493689 has been marked as a duplicate of this bug. ***
I have sent an appeal to Google to reactivate the API key. Since we do not know the reason for the constant blocking, I will impose restrictions. The first will be that you have to log in to Google again every time you call up the plugin. Maik
Git commit 45e16c4d7ba016fcb83436db8fa96e4d5edca86f by Maik Qualmann. Committed on 26/09/2024 at 19:39. Pushed by mqualmann into branch 'master'. do not save the Google service refresh token M +4 -3 core/dplugins/generic/webservices/google/gstalkerbase.cpp https://invent.kde.org/graphics/digikam/-/commit/45e16c4d7ba016fcb83436db8fa96e4d5edca86f
*** Bug 496636 has been marked as a duplicate of this bug. ***
Hi, I confirm this bug in 8.5.0 too. > The first will be that you have to log in to Google again every time you call up the plugin. Is this change supposed to help in any way?
We are still blocked by Google. I will write another appeal to Google this evening. This change is a shot in the dark, as we do not know the reason for the constant blocking. It is always the AUP-3 guideline that we are said to have violated. Does anyone have any ideas about what exactly the Google AI might not like about our Google Export Tool? https://developers.google.com/photos/library/guides/acceptable-use#permission Maik
(In reply to Maik Qualmann from comment #9) > We are still blocked by Google. I will write another appeal to Google this > evening. > This change is a shot in the dark, as we do not know the reason for the > constant blocking. > > It is always the AUP-3 guideline that we are said to have violated. Does > anyone have any ideas about what exactly the Google AI might not like about > our Google Export Tool? > > https://developers.google.com/photos/library/guides/acceptable-use#permission > > Maik > In all other cases, bulk processing of media is not permitted. Is this relevant somehow?
*** Bug 499362 has been marked as a duplicate of this bug. ***
*** Bug 501401 has been marked as a duplicate of this bug. ***
*** Bug 501977 has been marked as a duplicate of this bug. ***