Hi,
This has broken our deployed application. We are using this value to understand whether a clickThrough has been set on the ad (but obviously not to execute the actual clickthrough). Merely trying to access this method is now causing an error to be thrown.
If this breaking change is intentional, can you please make it clear to me how we can stay ahead of such breaking changes so we have time to discuss and ensure our deployed apps wont suffer?
Perhaps I missed something, but I need to ensure this wont happen again.
Thanks,
Philip