Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GmailV1: servicebatch_delete_messages #891

Open
Press10 opened this issue Jul 16, 2020 · 2 comments
Open

GmailV1: servicebatch_delete_messages #891

Press10 opened this issue Jul 16, 2020 · 2 comments
Labels
type: question Request for information or clarification. Not an issue.

Comments

@Press10
Copy link

Press10 commented Jul 16, 2020

def batch_delete_messages(user_id, batch_delete_messages_request_object = nil, fields: nil, quota_user: nil, options: nil, &block)

I've been beating my head against this batch_delete_messages method for a bit now and finally managed to get it working by updating from:
batch_delete_messages_request_object = nil
to:
batch_delete_messages_request_object: nil

here is what some of my code looks:

messages_object = service.list_user_messages(user_id, q: "older_than:1d")
message_ids = []
if messages_object.result_size_estimate > 0
messages_object.messages.each do |message_id|
message_ids << message_id.id
end
end
message_ids

then using that array of message_ids like so:

service.batch_delete_messages(user_id,batch_delete_messages_request_object: {"ids": message_ids})

would this be the correct fix to get this working? or am i passing in the message ids in wrong?

@yoshi-automation yoshi-automation added triage me I really want to be triaged. 🚨 This issue needs some love. labels Jul 17, 2020
@danoscarmike danoscarmike added type: question Request for information or clarification. Not an issue. and removed 🚨 This issue needs some love. triage me I really want to be triaged. labels Jul 22, 2020
@fhinkel fhinkel assigned fhinkel and unassigned dazuma Dec 8, 2020
@fhinkel
Copy link

fhinkel commented Dec 8, 2020

Hi @Press10 , thank you for the detailed bug report. Unfortunately, this issue tracker has limited visibility and scope - basically, it's just for reporting issues with the samples contained here and is only watched by the folks who work on these samples.

We are happy to help you move this bug to venues where it'll get the attention of the appropriate product teams.

I'm going to close this issue because the folks who own this repo have no actionable way to resolve it directly, but please let us know if there's anything we can do to help!

@fhinkel fhinkel closed this as completed Dec 8, 2020
@dazuma dazuma reopened this Dec 8, 2020
@dazuma
Copy link
Member

dazuma commented Dec 8, 2020

Reopening as this appears to be client-related rather than service-related

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: question Request for information or clarification. Not an issue.
Projects
None yet
Development

No branches or pull requests

5 participants