We're using Revive Adserver 3.2.0 but this issue happened in OpenX 2.8.10, from which we've recently upgraded. In short, the issue is that *certain* zones are not rendering adverts in iOS devices (iPads, iPhones).
The invocation we're using for both is identical, apart from the zone ID. This works absolutely fine on all other browsers - including Chrome on Android - so this isn't a desktop/tablet specific thing, it is an iOS specific thing.
There's nothing different between the zones - no delivery restrictions or anything obvious like that - I literally cannot figure out why this is happening.
I've used the iOS Simulator in OS X along with Safari's debug mode; no JS errors or anything like that. It's simply not creating the IFRAME containing the banner image within the DOM - although the beacon is being created, so clearly some JS is getting executed. This is what I can see in the DOM on the one that's failing (ID 19):
Problems Rendering Ads On Ios (Ipad, Iphone Etc)
in Using Revive Adserver
Posted
Hi,
We're using Revive Adserver 3.2.0 but this issue happened in OpenX 2.8.10, from which we've recently upgraded. In short, the issue is that *certain* zones are not rendering adverts in iOS devices (iPads, iPhones).
This can be seen here on these demo pages:
http://www.ichild.co.uk/dbcheckad18.php - zone ID 18 - works fine
http://www.ichild.co.uk/dbcheckad19.php - zone ID 19 - doesn't show anything
The invocation we're using for both is identical, apart from the zone ID. This works absolutely fine on all other browsers - including Chrome on Android - so this isn't a desktop/tablet specific thing, it is an iOS specific thing.
There's nothing different between the zones - no delivery restrictions or anything obvious like that - I literally cannot figure out why this is happening.
I've used the iOS Simulator in OS X along with Safari's debug mode; no JS errors or anything like that. It's simply not creating the IFRAME containing the banner image within the DOM - although the beacon is being created, so clearly some JS is getting executed. This is what I can see in the DOM on the one that's failing (ID 19):