Hi Arieh,
Not sure why you need logs from our side as this issue can be easily
reproduced: if you have existing UNNAMED image asset in an account, the
same image cannot be uploaded to this account. The
error “NAME_REQUIRED_FOR_ASSET_TYPE” will be raised by API.
As for logs, we have a problem
Hi,
I faced the same issue and it was resolved after I installed API v10.
Images having a name can be recognized when uploaded to account and the
same image is exist in this account. But I think there is still an issue
with unnamed images. If an image existing in account has no name and same
Hi,
I faced the same issue and it was resolved after I installed API v10.
Images having a name can be recognized when uploaded to account and the
same images is exist in this account. But I thinks there is still an issue
with unnamed images. If an image existing in account has no name and same
Hi all,
Fortunately, we were able to resolve the issue by using the latest Java SDK
version (17.0.0) which uses the new API version 10.
When doing the calls to this API, we don’t receive the error anymore and
instead, the existing asset id is automatically reused when we upload the
same
My fastest solution was the following:
$error_message = str_replace(". Remove the existing asset first if you
would like to change the name of the asset.,
reason=CANNOT_MODIFY_ASSET_NAME}]","",str_replace("'", "",
$e->getMessage()));
$arr = explode(" ", $ error_message);
$size = sizeof($arr);
Lately I have been getting this error too.
I used to get it in the past by passing an asset name when creating the
asset, but then I realized that the asset name was optional, so not passing
the asset name solved the issue. However now I'm getting the issue again
even though I'm not passing
Has anyone tried upgrading the API to version 10? We are currently using
the legacy Adwords API and we cannot do the upgrade at the moment.
On Friday, February 11, 2022 at 11:32:50 PM UTC+1 adsapi wrote:
> Hi Luciano,
>
> Right now, parsing the error message is the way to handle this error.
Hi Anash - we are not receiving the error message with the duplicate ID. We
are using the v9 of the API.
Here is the error message we are receiving:
"The asset has a name which is different from an existing duplicate that
represents the same content."
On Friday, February 11, 2022 at 3:32:50
Hi,
we have found a workaround on the creation of campaigns, let's first check
the existence of an image with a specific "name" and if it does not exist
we go to create it.
Previously we created them directly without "name" and the error of images
with same content never showed up.
Bye,
Hi,
we have found a workaround on the creation of campaigns, let's first check
the existence of an image with a specific "name" and if it does not exist
we go to create it.
Previously we created them directly without a "name" and the error of
images with same content never showed up.
Thx,
Someone wrote me in private asking which API version we were using. And
that's a very good point.
For this specific action, we're actually still using the legacy Google
AdWords API (v201809). So, if you don’t have the asset ID information in
the error message, you can’t use the same workaround
For some reason, my last message was deleted. I'm pasting the core
information of the message again below.
Just to share a detail I’ve noticed, I see that in the Google Ads API v.10
release from Feb 9th a change was introduced as you can read on the latest
release note of Google Ads API
Hi Luciano,
Right now, parsing the error message is the way to handle this error. I'll work
with the team to try and introduce a better way to expose this error.
Cheers
Anash
ref:_00D1U1174p._5004Q2Hyur3:ref
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
Hi everyone,
In our case, we actually get an asset ID on the error message, as you can
see below. I've redacted the original values with to prevent
sharing sensitive information.
*[AssetError{super=AssetError.CANNOT_MODIFY_ASSET_NAME @
operations[0].operand.assetName; trigger:'There
Hi all,
we have this issue as well since 2 days.
We're using SDK v.16.0.2 which uses API v.9
It stops us from uploading any image which has ever been uploaded to our
accounts before because of the clashing asset names.
It would be great if you could take care.
Thanks and best regards
On
Yeah modifying image by changing pixel color or cropping kinda works as
ugly hack but google should fix this.
No way this is acceptable, what's worst we have more than 100K assets and
we dont know which asset is what,
so ability to find an asset and replace it, makes sense however current
Hi everyone. I have some strange and quick solution for this problem. I
CROP(cut) every uploaded image with some random width and height. And only
after that i upload that CROPED image as asset, and that image seems like
new unique image.
Ex. in PYTHON
# For 1.91:1 ratio
ratio = 191/100
#
Hello, we have the same problem starting this morning. We have not changed
anything on our code. What is the correct procedure for uploading an asset?
We have all campaigns stopped for this reason.
Thanks
Il giorno giovedì 10 febbraio 2022 alle 10:22:54 UTC+1 timo...@gmail.com ha
scritto:
>
Hi Mark,
I understand but this has immediate impact on our ability to run campaigns,
we are losing revenue, and can't find work around for this issue.
Main issue is that we have uploaded a lot of images and now we can't even
tell which are in conflict, and that makes it a big issue.
So any work
Hi All,
Same here after the update, I've try to change the name, and try to change
few color of some random pixels, but still give me the same error.
Have no ideas what shall do next to solve this
Cheers
Wing
On Thursday, February 10, 2022 at 2:21:04 PM UTC+8 timo...@gmail.com wrote:
> After
After today's update we are getting this error as well and no way to fix it
*Error: The asset has a name which is different from an existing duplicate
that represents the same content*
It stops us from running campaigns would be good to get some clarity around
this issue
Thanks
On Thursday,
Hi there, just wonder if any progress you 've made here for this topic.
It's Feb 2022 and I'm still facing the same error.
As another developer mentioned above
> Typically when getting a duplicate error you really expect to have the Id
or some reference that points you to the original
Hi James,
Thank you for reporting on how the hacky workaround works. You may monitor our
blog for an update on this popular request.
Reminder: Share your feedback about the Google Ads (AdWords) API! Take the 2021
Google Ads API and AdWords API Annual Survey
Regards,
Aryeh Baker
Google Ads
Just implemented a hack to modify a random pixel by a single blue (as in
RGBA) pixel value (254 vs 255 for example) and it seems to be working.
Not ideal...but workable.
On Sunday, November 28, 2021 at 7:48:55 PM UTC-10 James Grace wrote:
> I'm struggling with this same problem.
>
> The
I'm struggling with this same problem.
The combination of not being able to delete assets and not being able to
get the resource_name of the "duplicate" makes this a pretty significant
problem in my opinion.
Is there really no proposed work-around?
On Wednesday, November 17, 2021 at
Hi Meir,
Thanks for following up.
You may continue to follow our blog for updates. Should you have additional
concerns with the API, you may start a new thread and our team would be happy
to assist you.
Best regards,
Reminder: Share your feedback about the Google Ads (AdWords) API! Take the
Never mind, it's not fixed yet, the original asset was being returned
because I was using the same asset name when creating the asset :/
El miércoles, 17 de noviembre de 2021 a las 15:09:55 UTC+1, Meir Mouyal
escribió:
>
> Hey there,
>
> Is it possible that this has already been solved?
>
> I
Hey there,
Is it possible that this has already been solved?
I can't find anything in the blog, however now I seem to get the original
asset details as a result!
Thanks :D
El lunes, 15 de noviembre de 2021 a las 2:47:29 UTC+1, adsapi escribió:
> Hi everyone,
>
> Thank you for your follow
Hi everyone,
Thank you for your follow ups. I work with Aryeh and allow me to assist you as
well.
@Meir, you may try updating the pixel and let us know how it goes. Also, I've
taken note of your suggestion to have the ID or the original resource included
in the error for ease of
Hi Aryeh,
Wanted to share that I am running into the exact same problem this morning.
Looking forward to having this added to the API. I'll check the blog for
updates.
On Friday, November 12, 2021 at 8:27:06 AM UTC-7 adsapi wrote:
> Hi Meir,
>
> I work with Ernie and will assist you. I
Hey there,
Yeep... I've thought about filtering through a report but... it's not ideal
at all, I might just modify a pixel in the image and upload it.
Typically when getting a duplicate error you really expect to have the Id
or some reference that points you to the original resource, so it
Hi Meir,
I work with Ernie and will assist you. I reproduced this behavior of
CANNOT_MODIFY_ASSET_NAME when uploading duplicate image with a modification in
UploadImageAsset.java to upload the image with a name the second time around,
the error response didn't show which image was the
I'm getting the same error and I'm setting a different name, the error
message is correct.
How can I know though which is the original asset?
El lunes, 31 de mayo de 2021 a las 10:59:57 UTC+2, Google Ads API Forum
Advisor Prod escribió:
> Hi,
>
> Thank you for raising this concern.
>
> If you
Hi,
Thank you for raising this concern.
If you are looking for a way to get the value of data field, then I am afraid
that this is not possible as this field is for mutate only.
However, it appears that the error did not occurred because you've uploaded the
same image, rather, this error
34 matches
Mail list logo
