Obsolete
Status Update
Comments
zh...@ed.bio-protocol.org <zh...@ed.bio-protocol.org> #2
Metadata
- Summary: The Directory API's users.list method is inconsistently returning a nextPageToken when using the query parameter, and the starts with operator is not working for the orgDepartment field.
- Tags:
,directory-api ,users-list ,next-page-token ,query-parameter ,org-department starts-with-operator
Additional resources:
https://issuetracker.google.com/savedsearches/566232?hl=it https://developers.google.com/drive/api/reference/rest/v3/files/list https://developers.google.com/admin-sdk/directory/v1/.../manage-users https://developers.google.com/admin-sdk/directory/reference/rest/v1/.../list https://stackoverflow.com/.../want-admindirectory-users-list-more-then-500... https://stackoverflow.com/.../drive-list-files-doesnt-have-nextpagetoken-wh... https://stackoverflow.com/.../how-to-resolve-the-missing-information-probl...
bl...@google.com <bl...@google.com> #3
Automated by Blunderbuss job workspace-devrel-public-issue-tracker-blunderbuss-autoassigner for config assign for component 191635.
jp...@google.com <jp...@google.com> #4
nextPageToken randomly disappear depending on the query.
It's only returned if there is another page.
Also the starts with operator doesn't work on orgDepartment :
Can you open another bug for this.
Description
We are encountering an issue with the Gmail API where some emails are sent with garbled characters.
Issue Description: The issue occurs intermittently. The same email (identical content, sender address, and recipient) will sometimes be sent with garbled characters.
We are using Go to interact with the Gmail API. The code snippet for generating the raw email is:
It would be great if you could help us with solving this problem. Thank you!