Closed MeisterMichael closed 2 years ago
One other unusual thing is that the generated refresh token begins with "1//" (one then two forward slashes) rather than the usual "1/" (one then a single slash)
Version 13.0.0 doesn't support any current API versions. If you don't specify a version manually, then it will use the latest version it knows about, which for 13.0.0 seems to be v8 of the API, not v11.
Update to the newest version of the gem and try again.
Version 13.0.0 doesn't support any current API versions. If you don't specify a version manually, then it will use the latest version it knows about, which for 13.0.0 seems to be v8 of the API, not v11.
Update to the newest version of the gem and try again.
I know the api version because it is shown in the debug warning.
My mistake I am using version 18.0.0 not 13.0.0
Here are the google gems in my gemlock
google-ads-googleads (18.0.0)
gapic-common (~> 0.6.0)
google-protobuf (>= 3.19.4, < 4.0)
google-api-client (0.53.0)
google-apis-core (~> 0.1)
google-apis-generator (~> 0.1)
google-apis-core (0.7.0)
addressable (~> 2.5, >= 2.5.1)
googleauth (>= 0.16.2, < 2.a)
httpclient (>= 2.8.1, < 3.a)
mini_mime (~> 1.0)
representable (~> 3.0)
retriable (>= 2.0, < 4.a)
rexml
webrick
google-apis-discovery_v1 (0.11.0)
google-apis-core (>= 0.7, < 2.a)
google-apis-generator (0.9.0)
activesupport (>= 5.0)
gems (~> 1.2)
google-apis-core (>= 0.7, < 2.a)
google-apis-discovery_v1 (~> 0.5)
thor (>= 0.20, < 2.a)
google-protobuf (3.21.3-x86_64-darwin)
googleapis-common-protos (1.3.12)
google-protobuf (~> 3.14)
googleapis-common-protos-types (~> 1.2)
grpc (~> 1.27)
googleapis-common-protos-types (1.3.2)
google-protobuf (~> 3.14)
googleauth (1.2.0)
faraday (>= 0.17.3, < 3.a)
jwt (>= 1.4, < 3.0)
memoist (~> 0.16)
multi_json (~> 1.11)
os (>= 0.9, < 2.0)
signet (>= 0.16, < 2.a)
grpc (1.48.0-x86_64-darwin)
google-protobuf (~> 3.19)
googleapis-common-protos-types (~> 1.0)
@mcloonan see above updated info
The internal error based on that request ID is: RequestError.INVALID_CUSTOMER_ID
Try specifying the customer ID without dashes.
@mcloonan Thanks! That was driving me mad.
Now I am getting this error. I thought I went through the process, with the authentication example, to get permissions. What am I missing?
...
W, [2022-07-27T09:38:51.652766 #16876] WARN -- : CID: 5562396321, Host: googleads.googleapis.com:443, Method: /google.ads.googleads.v11.services.GoogleAdsService/SearchStream, IsFault: yes, Request ID: 071fztjh6i_gYS10li5RkA
...
GRPC::PermissionDenied: 7:The caller does not have permission. debug_error_string:{UNKNOWN:Error received from peer ipv4:142.251.40.42:443 {grpc_message:"The caller does not have permission", grpc_status:7, created_time:"2022-07-27T09:38:51.650346-07:00"}}
...
Again, the internal error message provides more details:
The developer must sign the terms of service. They can be found here: ads.google.com/aw/apicenter
Now I'm just curious why these errors aren't rendering properly for you. They usually do for me when I make requests. I wonder if you make the logging more verbose, will you see these error messages?
@mcloonan how do I make my logging more verbose?
In your config, instead of
c.log_level = 'WARN'
Try:
c.log_level = 'INFO'
Or even:
c.log_level = 'DEBUG'
"DEBUG" is the most verbose, but "INFO" should probably be sufficient for this case.
Describe the bug:
When making any API call I get the following error: GRPC::InvalidArgument: 3:Request contains an invalid argument.. debug_error_string:{UNKNOWN:Error received from peer ipv4:142.251.40.42:443 {created_time:"2022-07-27T09:00:50.439061-07:00", grpc_status:3, grpc_message:"Request contains an invalid argument."}}
I downloaded the JSON file for my oath credentials, then used the authentication example (https://github.com/googleads/google-ads-ruby/tree/main/examples/authentication) to generate the refresh token, however every time I run any request I get the above error.
Steps to Reproduce:
Expected behavior: Get a response
Client library version and API version: Client library version: 18.0.0 (not 13.0.0) Google Ads API version: v11