Fixed
Status Update
Comments
jf...@google.com <jf...@google.com> #2
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.
jf...@google.com <jf...@google.com>
jf...@google.com <jf...@google.com> #3
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.
Description
For issues with the Google Photos app, please see:
-----------------------
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:
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 provide all of the following:
-----------------------------------------------------------------------------------------------------------------------------
A short description of the issue:
The JSON returned from API call (
It is very typical to write DTO class to match with the published object spec (
A small code sample that reliably reproduces the issue. The sample should run as-is or with minimal setup.
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. Just follow the description above, very easy understand.
2.
3.
What is the expected output? What do you see instead? If you see error messages, please provide them.
isWriteable should be included in the response JSON after an album is created.
Please provide any additional information below.