Status Update
No update yet.
Comments
jf...@google.com
Thank you for the very detailed and comprehensive issue report!
Just to confirm - are all media items shown in the Google Photos apps (and with the correct dates)?
I have forwarded it to our engineering team for further investigation. We will reach out when we have any updates or have any further follow-up questions.
gu...@gmail.com
I have found cases with more recent date ranges where more than 2 pages are returned, but the last page is still an empty response and not all of the expected media items have been returned yet.
In one particular case is when searching around 2018-08-31 in my library. On that day I have 294 images and videos which show in the Google Photos site. When I execute a search for 2018-08-30 to 2018-08-31, I receive 9 pages with a total of 210 media items. The last page includes a nextPageToken, but if I retrieve that next page it returns an empty response. Interestingly, if I add a day to the search, 2018-08-30 to 2018-09-01, then only 183 images are retrieved before encountering an empty page response. I have tried other various date ranges including Aug 31, starting as early as Aug. 1st, and the most I have been able to retrieve is 210 images. When I change the end date from Aug. 31 to Sept. 1, the media items are returned in a slightly different order, but it always seems to end with the same file, P8310169.JPG. In the Google Photos site I compared this image to the surrounding images including those that are and are not returned. The photos are nearly identical, all of them taken together on the same camera with the same settings and uploaded together through Google Backup and Sync for Windows. There is no clear indication why it would stop at that file without returning the next few in sequence.
I have also found 6 other 1-month date ranges between 2016 and 2018 which also end in an empty responses when paging through the results and where not all of the media items for the given range are never returned.
jf...@google.com
Hi, thanks for the response! Yes, all of the media items show on both the Google Photos site and Google Photos on Android including those that are not returned by the API. Please let me know if there is any additional data I can provide to help troubleshoot the issue.
za...@gmail.com
Hello! Is there any update on this issue? Please let me know if I can provide any additional information. Thanks!
Description
This is the issue tracker for developers using the Google Photos Library API:http://developers.google.com/photos
For issues with the Google Photos app, please see:https://support.google.com/photos/answer/6156065?hl=en
Before filing an issue, please read and follow these instructions carefully.
First, please search through existing issues to ensure that the bug has not already been reported. You can start the search here:https://issuetracker.google.com/savedsearches/5156057
If the issue has already been reported, you can click the star next to the issue number to subscribe and receive updates. We prioritize responding to the issues with the most stars. You can also comment on the issue to provide any details of your experience with it.
If your issue has not been reported, please delete this introduction and provide all of the following:
(Please enable Markdown for improved formatting of your report.)
Description
Using the baseUrl with "=dv" appended often, possibly always, fails for videos with slow motion sections.
Detailed description
I have written some java code that attempts to download some media from my google photos library. Some, but not all, of the videos are failing to download with this exception being thrown; "Server returned HTTP response code: 500 for URL: <product url>.
Looking at the videos in question it seems they are were all recorded with my Google Pixel 4a phone, using it's 1/8 slow motion setting and uploaded from that device, at "saver" quality.
The following is java code from my program where the variable "item" is a Media item returned by a call to PhotosLibraryClient.listMediaItems. The exception I am seeing is thrown by the call to openStream.