Fixed
Status Update
No update yet.
Comments
jf...@google.com
Thank you for your detailed report!
We'll take a closer look and let you know if we have any updates.
We'll take a closer look and let you know if we have any updates.
sa...@gmail.com
We have just clarified the resumable upload protocol in our documentation here: https://developers.google.com/photos/library/guides/resumable-uploads
Note that this is slightly different from our previous protocol for resumable uploads. Please let us know if you are still having trouble following this new guide. Our apologies, but the general flow should be very similar to the previous definition.
Note that this is slightly different from our previous protocol for resumable uploads. Please let us know if you are still having trouble following this new guide. Our apologies, but the general flow should be very similar to the previous definition.
ph...@gmail.com
Thanks for the updated documentation. I've given it a go and resumable uploads now seem to be working fine. Thanks.
sw...@gmail.com
I'm having this issue and it's really hurting user experience as most albums have more than 100 photos.
jf...@google.com
Re #4, this issue is unrelated to this report, this is being tracked in https://issuetracker.google.com/113559504 .
Re #5, you can load more than 100 media items by using pagination. See the guide here in our developer documentation:https://developers.google.com/photos/library/guides/list#pagination
Use the returned "nextPageToken" as part of your next request in the field "pageToken" to retrieve the next set of media items or albums.
Re #5, you can load more than 100 media items by using pagination. See the guide here in our developer documentation:
Use the returned "nextPageToken" as part of your next request in the field "pageToken" to retrieve the next set of media items or albums.
ri...@gmail.com
I have no problem with small responses, but the situation here is ridiculous. To go through my own entire library, I get a couple of thousand results with no issues. But then I get EMPTY results for the next 100 or so queries! It cannot take that long for the system to find the next ones.
jf...@google.com
A change has rolled out recently that should improve the fill rate for responses from the Library API. You should also encounter fewer empty pages, but they may still occur.
I'll close this issue, but please let us know if you are still seeing poor fill rates for requests or you are still seeing an excessive number of empty result pages and we can reopen this issue.
Thanks for your patience!
I'll close this issue, but please let us know if you are still seeing poor fill rates for requests or you are still seeing an excessive number of empty result pages and we can reopen this issue.
Thanks for your patience!
ch...@gmail.com
I am experiencing this issue still. I am using the Javascript SDK.
I request 24 and get 12, I request 48 and get 24.
Is there no way we can make pageSize be max cap so it fills the request?
I request 24 and get 12, I request 48 and get 24.
Is there no way we can make pageSize be max cap so it fills the request?
Description
While using the mediaItems.search API if we do not pass any "pageSize" attribute, all photos are returned as expected. However, if we pass a "pageSize" then the number is halved. E.g. passing 30 returns 15 results, 20 returns 10 and 10 returns 5.
The calls to the API that lead to the error. Include the sequence of calls, including request headers and body.
Do not include any personal information, authentication secrets, media item or album IDs.
What steps will reproduce the problem?
1. Call the
2. Now call
3. Looking for photos within an album doesn't display this issue.
4. This can be tested out in the "Try this API" section as well.
What is the expected output? What do you see instead? If you see error messages, please provide them.
The "pageSize" value should be respected for the mediaItems.search API instead of showing half of the photos.
Please provide any additional information below.