Since the 201806 api release we experience PolicyFindingError (instead of PolicyViolationError before the 201806 release) when creating Expanded Text Ads.
The problem we have with the PolicyFindingError is that the field which triggered the error in the fieldPath is absent. For example when creating an Expanded Text Ad with with headline1 containing '!!' the Adwords Ads api returns: "operations[0].
operand.ad" as fieldPath in the PolicyFindingError.
When we create for example an Expanded Text Ad with path2 containing an ":" the FieldPath in the StringFormatError is: "operations[0].operand.ad.path2"
Could this be fixed? Or is there a workaround for this problem?
Regards,
Hendrik Boon