Bug 403819 - Export to Google Photos not working (bad request)
Summary: Export to Google Photos not working (bad request)
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-WebService-Google (show other bugs)
Version: 5.9.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-01 07:26 UTC by 0711onetime
Modified: 2019-03-25 15:17 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.1.0

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description 0711onetime 2019-02-01 07:26:45 UTC 
cannot export to google photos


STEPS TO REPRODUCE
1. ALT+SHIFT+P (export to picasa/google photos)
2. Change account (sorry I am using digikam in german so I am not sure if this is the right translation: "Zugang wechseln"
3. log out and log in to my google account
4. kipi-plugins may acces my google photo account (agree)
5. copy the code in digkam, press enter
6. error message: "Error transferring https://picasaweb.google.com/data/feed/api/user/default - server replied: Bad Request"
7. press ok
8. tried with multiple google accounts, always same result

OBSERVED RESULT
kipi-plugins has access to google account/photo (verified in my google account third party apps) but no upload possible

EXPECTED RESULT
export photos to google photo account

SOFTWARE/OS VERSIONS
Windows: WIN 10 (1809) 17763.253
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Maik Qualmann 2019-02-01 07:31:48 UTC 

*** This bug has been marked as a duplicate of bug 403569 ***
Comment 2 caulier.gilles 2019-03-24 18:32:55 UTC 
Not reproducible with 6.1.0

Gilles Caulier
Comment 3 0711onetime 2019-03-25 15:11:51 UTC 
(In reply to caulier.gilles from comment #2)
> Not reproducible with 6.1.0
> 
> Gilles Caulier

So, it is fixed with the (snapshot) release 6.1.0? Does it works in 6.0.0 as well?
Comment 4 caulier.gilles 2019-03-25 15:17:03 UTC 
6.0.0 must have the fix has i know. At least 6.1.0 will do the job.

Gilles Caulier