sofisl

Marking it as eol so we can search for the tag and bring up what we should do.

This looks good to me, as long as tests pass as well :) Thank you!

Hi @judblackburn, would you mind providing a project and/or instructions to reproduce? I haven't encountered any issues with `gts fix` in my own repos, so just want to make sure...

Thanks for adding @judblackburn. I can reproduce the issue, will dig into it.

Hello! We are migrating this repo over to google-cloud-node. If this is still a concern for you, we ask you kindly reopen the issue there. Thank you very much!

Hello! We are migrating this repo over to google-cloud-node. If this is still a concern for you, we ask you kindly reopen the issue there. Thank you very much!

Also posting this thread for more reference: https://github.com/googleapis/google-api-nodejs-client/issues/2515 Thank you @OrKarstoft!

I agree. I think this is a duplicate, [this is the correct answer](https://github.com/googleapis/google-api-nodejs-client/issues/2405#issuecomment-721512809). Apologies that this appears to be confusing documentation. It seems that the Unix timestamp should be passed...

Sorry that this took so long, it seems like it's been published: https://www.npmjs.com/package/@googleapis/playintegrity

Hi @Apollon77, I believe you're getting unhandled rejections due to the mixing of chaining and async functions. I've reproduced your code with a similar example, see below: ``` const {google}...