I have an issue with the Google Ads v16 version. This particular method is causing problems, and I can't update either the descriptions or the headlines. Here is my code, taken from an example of the API for this specific version:

Api reference: https://developers.google.com/google-ads/api/samples/update-responsive-search-ad

If I remove the ResponsiveSearchAdInfo method, for example, to only update the final_urls, this works successfully.

The error it gives me is the following:

error: {     "message": "Request contains an invalid argument.",     "code": 3,     "status": "INVALID_ARGUMENT",     "details": [         {             "@type": "type.googleapis.com\/google.ads.googleads.v16.errors.GoogleAdsFailure",             "errors": [                 {                     "errorCode": {                         "requestError": "UNKNOWN"                     },                     "message": "The error code is not in this version.",                     "location": {                         "fieldPathElements": [                             {                                 "fieldName": "operations",                                 "index": 0                             },                             {                                 "fieldName": "update"                             },                             {                                 "fieldName": "resource_name"                             }                         ]                     }                 }             ],             "requestId": "qub0AMx1K3uIn8f0pUvKlg"         }     ] } 

It seems strange to me that it references resource_name, as without changing anything in that line, I send the parameter to change the URL, and it works fine. By the way, in my controller, I'm not handling this as a static function, like the example shown in the API.

This is mi code:

    $ad = new Ad([         'resource_name' => ResourceNames::forAd($customerId, $adId),         'final_urls' => [$finalUrls],         'final_mobile_urls' => [$finalUrls],           'responsive_search_ad' => new ResponsiveSearchAdInfo([             // Update some properties of the responsive search ad.             'headlines' => [                 new AdTextAsset([                     'text' => 'Cruise to Pluto #' ,                     'pinned_field' => ServedAssetFieldType::HEADLINE_1                 ]),                 new AdTextAsset(['text' => 'Tickets on sale now']),                 new AdTextAsset(['text' => 'Buy your ticket now'])             ],             'descriptions' => [                 new AdTextAsset(['text' => 'Best space cruise ever.']),                 new AdTextAsset([                     'text' => 'The most wonderful space experience you will ever have.'])             ]         ]),            ]); 

Any help is welcome. Thank you!

Got a issue with Meta for WhatsApp Here is the error message : The error message you're encountering in the WhatsApp Cloud API is: "(#200) You do not have permission to access this field."
This typically indicates that the user account or the access token being used lacks the necessary permissions to access the specific field mentioned in the error message. To resolve this issue, you may need to review the permissions associated with your account or access token and ensure that they have the appropriate permissions to access the field in question.
Further, if the issue still persists then kindly contact the Meta support team for the same.
Could you please resolve

Dear Developer Community,
I am currently facing a challenge with the Facebook API, specifically the GET /{live-video-id}/live_comments feature. My aim is to fetch live comments from a specific Facebook Live video. I have been following the official documentation and using the example code provided:
var source = new EventSource("https://streaming-graph.facebook.com/{live-video-id}/live_comments?access_token={access-token}"); source.onmessage = function(event) { // Code to handle event.message };
Please refer to my pictures for error conditions
However, every time I run this script, I encounter an Error 503 response. Despite trying various troubleshooting steps, the issue persists, which leads me to suspect a possible problem with the API itself.
I am reaching out to ask if anyone in the community has faced a similar issue and how you managed to resolve it. Any advice or shared experiences would be greatly appreciated.
Thank you all for your time and assistance.
Best regards,
Hank