I use the version 201710 and about a week ago I started getting errors CriterionError.INVALID_PROXIMITY_ADDRESS. I have some address and sometimes it works for it correctly, and sometimes I get this error. What is going on? It does seem as bug on your side.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> <soap:Header> <ResponseHeader xmlns="https://adwords.google.com/api/adwords/cm/v201710";> <requestId>00056b996898a9c80a3713077f03c18b</requestId> <serviceName>CampaignCriterionService</serviceName> <methodName>mutate</methodName> <operations>2</operations> <responseTime>113</responseTime> </ResponseHeader> </soap:Header> <soap:Body> <soap:Fault> <faultcode>soap:Client</faultcode> <faultstring>[CriterionError.INVALID_PROXIMITY_ADDRESS @ operations[0].operand.criterion.address, CriterionError.INVALID_PROXIMITY_ADDRESS @ operations[1].operand.criterion.address]</faultstring> <detail> <ApiExceptionFault xmlns="https://adwords.google.com/api/adwords/cm/v201710";> <message>[CriterionError.INVALID_PROXIMITY_ADDRESS @ operations[0].operand.criterion.address, CriterionError.INVALID_PROXIMITY_ADDRESS @ operations[1].operand.criterion.address]</message> <ApplicationException.Type>ApiException</ApplicationException.Type> <errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:type="CriterionError"> <fieldPath>operations[0].operand.criterion.address</fieldPath> <fieldPathElements> <field>operations</field> <index>0</index> </fieldPathElements> <fieldPathElements> <field>operand</field> </fieldPathElements> <fieldPathElements> <field>criterion</field> </fieldPathElements> <fieldPathElements> <field>address</field> </fieldPathElements> <trigger/> <errorString>CriterionError.INVALID_PROXIMITY_ADDRESS</errorString> <ApiError.Type>CriterionError</ApiError.Type> <reason>INVALID_PROXIMITY_ADDRESS</reason> </errors> <errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:type="CriterionError"> <fieldPath>operations[1].operand.criterion.address</fieldPath> <fieldPathElements> <field>operations</field> <index>1</index> </fieldPathElements> <fieldPathElements> <field>operand</field> </fieldPathElements> <fieldPathElements> <field>criterion</field> </fieldPathElements> <fieldPathElements> <field>address</field> </fieldPathElements> <trigger/> <errorString>CriterionError.INVALID_PROXIMITY_ADDRESS</errorString> <ApiError.Type>CriterionError</ApiError.Type> <reason>INVALID_PROXIMITY_ADDRESS</reason> </errors> </ApiExceptionFault> </detail> </soap:Fault> </soap:Body> </soap:Envelope> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/2bff66d4-dedf-4538-b798-f0e966dc233e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
