Request is 'sometimes' missing OAUTH2 token

[Dev Eloper]

Hello,

Since today our Desktop application is experiencing some unexpected issues with regards to the error:

vendor/google/gax/src/ApiException.php - 139 - {
    "message": "Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https:\/\/developers.google.com\/identity\/sign-in\/web\/devconsole-project.",
    "code": 16,
    "status": "UNAUTHENTICATED",
    "details": [
        {
            "@type": "request-id",
            "data": "[[REQUESTID(can be provided)]]"
        }
    ]
}

The weird thing is that our application uses the php libraries provided by Google and most of the time requests go through fine, but then sometimes the same requests fail with above error.

Authentication is done the same as well, we use the provided libraries to create the credential objects and client.

This only started happening today without us changing any of our code.

Hopefully someone can shed some light on this situation,

Teun

[CFJ]

I've been seeing this as well over the last 24-36 hours.  We've been on the Ads API v10 using the .NET client library for several weeks with zero authentication issues.  Yesterday, we began seeing a few of these "Request is missing required authentication credential" errors.  99.9% of our requests are going through just fine, so this feels like a random bug on Google's end.

[Google Ads API Forum Advisor]

Hi there,

Thanks for reaching out to the Google Ads API Forum.

For us to investigate further, could you provide us with the complete request and response logs with the request-id, so our team can better check?

For the client library, logging can be enabled by navigating to the Client libraries > Your client library (ex Java) > Logging documentation, which you can access from this link. You may then send the requested information 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.

Regards,

Yasar Google Ads API Team

ref:_00D1U1174p._5004Q2asDqh:ref

[Christian H.]

Hi,

I'm experiencing the same (with the java client lib). I saw this error irregularly from time to time in the past (once or twice a week). But starting on May 11th it occurs much more often.

Regarding the logs: I try to create one. However, this is difficult because the error only occurs spontaneously and I really make a lot of changes. I need to see if I can handle the size of the log files

Best regards

Christian

[Killian Lanigan]

I've also been experiencing this issue lately and also have seen it occurring more often.

[Google Ads API Forum Advisor]

Hello Christian,

Thank you for getting back to us. Could you please verify that you are using the correct credentials? Our Quickstart takes you through the process of acquiring the correct set you need. For example, the above response failure shows that the user has sent invalid authentication credentials.

If the issue still persists, kindly share the complete request and response logs with request-id and login-customer-id generated on your end, so our team can investigate the issue further. 

For the client library, logging can be enabled by navigating to the Client libraries > Your client library (ex. Java) > Logging documentation, which you can access from this link.

Please send the requested details via the Reply privately to the author option. If this option is not available, you may send the details directly to our googleadsa...@google.com alias by referring to this thread.

Best Regards,

Jakeia Google Ads API Team

ref:_00D1U1174p._5004Q2asDqh:ref

[Christian H.]

Hi Jakeia,

It was definitely no problem on my side: as I wrote I use the java google-ads client-lib and the error only occurred irregularly (User CFJ said 0,1% of the requests have been affected). It must have been some issues with your authorization-checker.

But the problem seems to have been solved, the last time I received the UNAUTHENTICATED error was on Friday, 2022-05-13 09:50 CET.

Best regards

Christian

[CFJ]

Like Christian, I'm seeing that this appears to have resolved.  The last UNATHENTICATED error Google returned for us was on Friday morning as well.