Infeasible
Status Update
Comments
jp...@google.com <jp...@google.com> #2
Generated Metadata
- Summary: The developer is reporting an issue with the Drive API v3 files.list endpoint. The API is returning an empty list of files, but a non-null nextPageToken, resulting in missing files when paginating through a Shared Drive. This behavior is intermittent.
- Tags:
Additional resources:
https://developers.google.com/drive/api/reference/rest/v3/files/list https://stackoverflow.com/.../cannot-get-google-drive-api-v3-to-return-next... https://stackoverflow.com/questions/.../list-request-page-size-being-ignored https://stackoverflow.com/.../drive-api-files-list-returning-nextpagetoken-wi... https://stackoverflow.com/questions/.../files-list-yields-unpredictable-results
You can
bl...@google.com <bl...@google.com> #3
Automated by Blunderbuss job workspace-devrel-public-issue-tracker-blunderbuss-autoassigner for config assign for component 191650.
jp...@google.com <jp...@google.com> #4
There can be additional filtering that happens after the token has been generated that leads to these results.
el...@edutechsg.com <el...@edutechsg.com> #5
When I call the api, no query changed, always the same one, just set "nextPageToken" to get next page result. could you explain more? and any suggestions when this happened?
thanks
Description
Hi everyone,
I am using "GEThttps://www.googleapis.com/drive/v3/files " to list all files of a Shared Drive.
API reference: https://developers.google.com/drive/api/reference/rest/v3/files/list
I set "pagesize" as 1000, and check "nextPageToken" property in result. If "nextPageToken" is not null or empty, then call list API to get next page result.
But there is a case, the "Files" property in result is empty, but "nextPageToken" has value. If no more result, "nextPageToken" from last call should be null or empty. In this case, the result missing some files. is it a bug?
This case doesn't happen every time, but I am sure, when it happened, the result missing some files.
thanks