The error code is not in this version

[Vytautas Smilingis]

Hello, we started receiving this error for a few of our clients. I was trying to setup request logging as per the docs, but nothing was logged. We do have a request ID: bNklNVkIz392VhtbuDfLzg
API version: v14

Query: "SELECT expanded_landing_page_view.expanded_final_url, metrics.clicks, metrics.impressions FROM landing_page_view WHERE segments.date BETWEEN '2023-07-04' AND '2023-08-02' AND metrics.impressions > 0 ORDER BY metrics.impressions DESC".

Error:
array:1 [ 0 => array:1 [ "error" => array:4 [ "code" => 400 "message" => "Request contains an invalid argument." "status" => "INVALID_ARGUMENT" "details" => array:1 [ 0 => array:3 [ "@type" => "type.googleapis.com/google.ads.googleads.v14.errors.GoogleAdsFailure" "errors" => array:1 [ 0 => array:2 [ "errorCode" => array:1 [ "requestError" => "UNKNOWN" ] "message" => "The error code is not in this version." ] ] "requestId" => "bNklNVkIz392VhtbuDfLzg" ] ] ] ] ] While writing this, I figured out that this request succeeds if I remove SummaryRowSetting. Usually if our query includes metrics, we also set SummaryRowSetting as SUMMARY_ROW_WITH_RESULTS. Why would this start failing now?

[Google Ads API and AdWords API Forum]

Re-posting the last inquiry (https://groups.google.com/g/adwords-api/c/SiIFcfovvAc) from the forum as it wasn't routed to our support queue.

Regards,
Google Ads API Team

[Google Ads API and AdWords API Forum]

Hi everyone,

Thank you for raising this concern to the Google Ads API support team. Please excuse us for only getting back now as your message failed to be routed to our support queue.

In order for our team to have a better understanding about this behavior and can provide precise recommendations, can you please provide the complete API logs below?

• request - https://developers.google.com/google-ads/api/docs/concepts/field-service#request
• response - https://developers.google.com/google-ads/api/docs/concepts/field-service#response
• request ID - https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id
• request header - https://developers.google.com/google-ads/api/docs/concepts/call-structure#request_headers

You may then send the requested logs via the Reply privately to author option. If this option is not available, you may send the details directly to our googleadsa...@google.com alias instead.

Note that these logs can be requested or provided to the developer handling the Google Ads API transactions when logging of the API requests has been enabled. You may check here (https://developers.google.com/google-ads/api/docs/best-practices/logging#client_library_logging) for the specific guideline to enable it.

For REST interface requests, you can enable logging via the curl command by using the -i flag. This will cause the tool to include HTTP response headers in the output.

Regards,
Google Ads API Team

On Thursday, August 3, 2023 at 4:00:50 PM UTC+8 vyta...@whatagraph.com wrote:

[Vytautas Smilingis]

We're unable to set up logging. We tried it as per the docs, but nothing was logged. I tried debugging and saw that logger was registered as grpc interceptor, but still no logs even with successful requests. Can you guys verify that logging works with Google Ads PHP client?

Is request ID enough? bNklNVkIz392VhtbuDfLzg

[Google Ads API and AdWords API Forum]

Re-posting the last inquiry (https://groups.google.com/g/adwords-api/c/SiIFcfovvAc) from the forum as it wasn't routed to our support queue.

Regards,
Google Ads API Team

[Google Ads API Forum Advisor]

Hi,

Thank you for your response.

Can you confirm if this is the logging guide (https://developers.google.com/google-ads/api/docs/client-libs/php/logging) that you've tried in your end that doesn't log anything? We also confirm that this should be working properly as there are no reported errors that should affect the logging. However, if you still encountering a logging issue, you may create a new issue in the tracker on the client library (https://github.com/googleads/google-ads-php/issues) to further assist you, and you can return to us for the requested information previously privately.

Kindly note that, in July 2023, the Google Ads API client library for PHP (https://github.com/googleads/google-ads-php) will start requiring PHP version 8.0 or higher. 

This message is in relation to case "ref:_00D1U1174p._5004Q2nb0ca:ref"

Thanks,
 

Google Ads API Team

[Vytautas Smilingis]

Thank you for pointing me back to the client library GitHub. I searched the issues there and was able to configure logging. Turns out logging for REST is not supported, and I had forgotten to install gRPC extensions when I upgraded my PHP version.

I don't see Reply privately to author option here, so I will send the logs via email.

[Google Ads API Forum Advisor]

Hi Vytautas,

Thank you for the confirmation.

I can see that you have already sent the logs requested in a separate email with the same subject. With this, we would suggest continuing the discussion there and any further communications regarding this concern will be on that thread for better tracking of issues.

[Vytautas Smilingis]

Just following up in case someone else searches for this problem. After sending logs to Google Ads support email they were quick to identify that the issue was caused by setting summary_row_setting to “SUMMARY_ROW_WITH_RESULTS”. However, this was an error on API side and they quickly patched it. Everything works as expected now.