Fixed issues

Fixed in MR3 (bundle 1.0.3.124)

The extra-extra large banner ad size has changed from 320 x 53 pixels to 320 x 50 pixels, as per the MMA Standard Guidelines.

If the screen was closed before the banner component received the ad content, the banner component JavaScript engine continued to work in the background. Once there were about 100 screens closed before the banner was able to get its first ad, the user received an error message and the overall performance of the device was affected.

Fixed in MR3 (bundle 1.0.3.111)

On devices that are running versions of BlackBerry Device Software earlier than 6.0, the Advertising Service didn't properly handle blank banners that were returned from the ad network.

On some devices, if a user turned the device from landscape to portrait orientation multiple times, an ad sometimes appeared zoomed in.

On devices that are running versions of BlackBerry Device Software earlier than 5.0, if there was a Banner object in a HorizontalFieldManager, users wouldn't be able to scroll to the end of text-based ads and parts of the ads were truncated.

On some devices that are running BlackBerry 6, the focus border displayed on an ad without the ad being clickable.

On some devices that are running BlackBerry 6, if a user opened an application, lost connectivity to the wireless network, and regained connectivity while the application is still open, the application couldn't receive new ads.

On some devices, if a user didn't have access to a wireless network and the user clicked a Click-to-Phone ad to make a call, the application didn't display a message that stated that the wireless network was unavailable.

On devices that are running BlackBerry 6, if the placeholder image that you specified was larger than the ad that your application received, parts of the placeholder image might have still been visible after the ad loaded.

On devices that are running BlackBerry Device Software 5.0, if you created a placeholder image that was larger than the size of a Banner object, when the Banner object received an ad, part of the placeholder image might have still been visible.

On devices that are running versions of BlackBerry Device Software earlier than 5.0, if your application received a blank ad, the Banner object that contained the ad was not displayed properly on the screen.

Fixed in MR2.5 (bundle 1.0.0.85)

On some BlackBerry devices running BlackBerry Device Software 5.0, ads did not display correctly and a ClassCastException appeared in the event log.

Fixed in MR2 (bundle 1.0.0.84)

If you removed a Banner object from a screen without removing the containing field manager, ads wouldn't appear in other Banner objects.

When you added or removed a field manager from a screen that contained a Banner object, a NullPointerException would show up in the event log.

In some cases, when a user clicked a click-to-web ad, rather than open a website, the application displayed an 'Error loading link' message.

Fixed in MR1 (bundle 1.0.0.50)

There was no capability to display ad banners on popup dialogs and alerts.

If a "No Network Coverage" popup message appeared, the image of a progress indicator was always present.

On devices that were running versions of BlackBerry Device Software earlier than 5.0, when the Banner object did not receive any ads from the mediation layer, the fade in and fade out transition would still occur.

After a device user clicked a click-to-Contacts ad, when the confirmation dialog box appeared, if the user selected the text in the dialog box, the user couldn't click an option.

On some networks that didn't support the simultaneous use of voice and data, when a user opened an application while making a phone call, the application couldn't receive ads, and the application didn't display an error message.

Next topic: Known issues
Previous topic: New in this release

Was this information helpful? Send us your comments.