Hi Bojan,
Thank you for reaching out to us.
Can you confirm if you are implementing Native ads custom events? If yes, as per our documentation, callToActionView should be disabled. Kindly note, that our sample code disables user interaction for the UIButton that displays the call to action. If you use UIButtons to display native ad assets, you also need to disable their user interaction so that the Google Mobile Ads SDK can properly receive and process UI events. Because of this extra step, it's frequently best to avoid UIButtons entirely and use UILabel and UIImageView instead. Let me know if this is what you're looking for.
Regards,
|
||||||
|
||||||