uninitialized constant Google::Ads

[Santoni kho]

Hi, im using a ruby gem called google-ads-ruby to run my application, but I face the error uninitialized constant Google::Ads. However, the error goes away when I restarted my local server. Is there any ways to workaround this, as it happens everytime I modify my ruby code.

[Google Ads API Forum Advisor]

Hi Santoni,
 

Thanks for reaching out to the Google Ads API team. I hope you are doing well today.

To further investigate the issue, could you please provide the complete request and response? logs appear similar to the JSON Mappings in our REST documentation with additional headers and information such as request Id . Here are logging instructions for our Java , .NET , PHP , Python, Ruby and Perl Ads API Client Libraries.
 

If you are using our REST interface then the full multi line curl command line is a request log and adding curl command line option '-i' will also generate a response log. I ask this so our team further investigates your concern and provides specific recommendations on the issue.


You can provide it via Reply privately to the author option. If this option is not available, then send it instead on this email address googleadsa...@google.com.


Regards,

Darwin Google Ads API Team

ref:_00D1U1174p._5004Q2egpNr:ref

[Google Ads API Forum Advisor]

Hi Santoni,

Thanks for getting back to us.

I understand that request error comes out uninitialized constant Google::Ads, and happens for the Ruby client library upon modifying. Then this is more related to client library issues. You may also check here the required configuration for this library. If that doesn't help, then I would suggest you reach out to the Ruby client library owner by filing an issue on the issue tracker on the Issue tab of your client library on github, so that they can provide guidance on it.  

Regards,

Yasar Google Ads API Team

ref:_00D1U1174p._5004Q2egpNr:ref

[Google Ads API Forum Advisor]

Hi Santoni, 

I had to delete your last post as it exposed the developer token, and our team suggests resetting your developer token if it is exposed publicly. A reset will immediately invalidate your previous token, so any API requests using the old token will fail. However, a reset will not trigger a re-review and approval for the new developer token. You can start using the new developer token immediately. For more information, you may refer here:https://developers.google.com/google-ads/api/docs/best-practices/developer-token-reset?hl=en

[Santoni kho]

Hi, Thanks for support, will try to filing an issue on the issue tracker.