Hello Filipp,
I'll update this thread with any information I hear back. In the
meantime, if modifying the proxy class works around the issue I'd
recommend that you keep running with that modified version. It's
obviously something that should be fixed on the server to benefit the
whole developer
Hi Jeff, please notify me, if possible, when you hear back from the
API team.
Thank you!
Filipp
On Jan 5, 4:28 pm, "frakevich...@gmail.com"
wrote:
> Hi Jeff, this is the requestId: 8ea141994bd0d95b830e8da5e04b191d
> I was going against the adwords.google.com site.
>
> Thank you!
> Filipp
>
> On
Hi Jeff, this is the requestId: 8ea141994bd0d95b830e8da5e04b191d
I was going against the adwords.google.com site.
Thank you!
Filipp
On Jan 5, 4:15 pm, AdWords API Advisor
wrote:
> Hello Filipp,
>
> Interesting--if the SOAP service isn't honoring the return format
> specified in the WSDL then t
Hello Filipp,
Interesting--if the SOAP service isn't honoring the return format
specified in the WSDL then that's something that would need to be
addressed.
Could you pass along the requestId from the SOAP response so that I
can grab the message from the logs and pass it on to the core
enginee
Hi Jeff, thank you for getting back to me!
I am using only the basic geo locations.
I inspected the response from Google and the geo locations are in fact
being sent back. This means that the response is not deserializing
properly. So I investigated the issue a bit further and found this:
The wsd
Hello Filipp,
Not all geo-targets can be represented in the AdWords API. For
example, the API doesn't support arbitrary polygons as geo-targets,
although you can create those using the AdWords web interface. Does
that sound like it may be the cause of what you're seeing?
If you have one or mor
