SUMMARY STEPS TO REPRODUCE 1. Goto: Import from Google Photos 2. User is prompted to enter email address to authenticate OBSERVED RESULT User is shown the following error message with no "This browser or app may not be secure. Try using a different browser. If you’re already using a supported browser, you can refresh your screen and try again to sign in." EXPECTED RESULT User should be able to provide password and 2nd factor authentication. I've generated the access token to use the Google Photos API in the past. The ability to manually provide the token could be a good workaround by using a SOFTWARE/OS VERSIONS macOS: 10.15.7 ADDITIONAL INFORMATION
Please try with digiKam 7.2.0 RC pre-release: https://files.kde.org/digikam/ Gilles Caulier
I can confirm the problem here on Linux using the QWebEngine. After a short research, Google no longer allows a browser based on the Chromium Framework within an app. We may have to port our App to a "Progressive Web App". Maik
Git commit 9a100bf354ee00c1eadb6b7bdcbdc0c6e385fad4 by Maik Qualmann. Committed on 22/01/2021 at 07:15. Pushed by mqualmann into branch 'master'. first workaround to fix login to Google with QWebEngine M +3 -0 core/libs/dialogs/webbrowserdlg.cpp https://invent.kde.org/graphics/digikam/commit/9a100bf354ee00c1eadb6b7bdcbdc0c6e385fad4
Git commit 954697619646385190f333b9c4b7aeaeda785bd2 by Maik Qualmann. Committed on 22/01/2021 at 18:30. Pushed by mqualmann into branch 'master'. change user agent from QWebEngine browser FIXED-IN: 7.2.0 M +2 -1 NEWS M +17 -1 core/libs/dialogs/webbrowserdlg.cpp https://invent.kde.org/graphics/digikam/commit/954697619646385190f333b9c4b7aeaeda785bd2
It looks like that if Google finds the string "Chrome" it is probably making specific Chrome API calls that QWebEngine does not support. The Chromium Browser, although it uses the same User Agent, is not affected. QWebKit is still working now. We'll have to keep an eye on it. Maik