Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Known Issues

Known Issues

Updated: May 2, 2014

Published: May 2, 2014

This topic provides information about issues that developers may experience when using the SDK.

Visit The Support Forums For Up-to-Date Information

For current information about issues that developers are facing, please see the Microsoft Advertising support forum.

Use The Correct Library for the OS You Are Targeting

If you install more than one of the current versions of the Microsoft Advertising SDK, all of the libraries will be available in Visual Studio's Reference Manager. Make certain that the SDK library you select in Visual Studio's Reference Manager is the one to use for the OS and framework that you are using to develop your app.

Side-by-Side Installation With Prior Versions Is Not Supported

If you have prior versions of the Advertising SDK—especially beta versions—installed on the same machine with the latest version, you will receive errors at design time and your app may encounter run-time errors. The installer will remove and install over prior versions of its own SDK (OS and Framework). If you circumvent these operations, neither the old or new SDK will work.

APIs Not Available On The Platform You Are Targeting May Not Be Visible in Visual Studio

If you are writing a app using Visual Studio 2012 and targeting the Windows Phone 7.x platform, APIs in the Windows 8 library that are only available to Windows 8 apps may not be displayed in Visual Studio's Object Browser or Intellisense. This behavior is by design for Visual Studio, so you will see this behavior in all controls.

AdControl Does Not Refresh When It Is Not Visible to the User

If the AdControl is not visible to the user (for example if it has been collapsed or hidden) it will not refresh while in that state. This behavior is by design.

AdControl May Be In A Collapsed State Or Opacity Set To Zero

Some state changes and errors, including a no ad error, might:

  • Collapse the AdControl, so the inherited property Visibility may be set to Collapsed.

  • Make the AdControl not visible, so the inherited property Opacity is set to 0.

Setting the property IsAutoCollapseEnabled to TRUE might have no effect visually since the AdControl will be made transparent and may appear collapsed.

If you are having issues with the state of the AdControl, check to see if the control's Visibility property (inherited) is in a Collapsed state (see http://msdn.microsoft.com/en-us/library/system.windows.uielement.visibility.aspx). Also check to see if the control's Opacity property (inherited) is set to 0 (see http://msdn.microsoft.com/en-us/library/system.windows.uielement.opacity.aspx).

Report the issue and your scenario to product support.

Video Ads May Not Pause During Incoming Phone Call

If a video ad is playing while an incoming phone call occurs the video may not pause. Any audio from the ad will be muted during the call, but the video may continue to play.

Video Ads May Continue To Play When Phone Is Locked

Locking the phone while a video ad is playing might not suspend the video ad.

Emulator Issues

This section describes known issues with the SDK when running the Windows Phone emulator in Visual Studio.

Click-To-Web May Not Navigate To URL

When an ad launches the web browser on the emulator, the browser will start but may not navigate to the destination URL.


This section describes known errors that developers have encountered when using the Microsoft Advertising SDK.

Error: “Creative size does not fit AdControl size.”

The Visual Studio Visual Designer may remove width/height attributes from the AdControl’s XAML or Silverlight code. In that case, the AdControl stops displaying ads and will report an error with the description "Creative size does not fit AdControl size." Set the width and height values of the AdControl equal to or greater than the ad unit size you chose in pubCenter.

No Ads

There are many reasons your app may receive no ads, such as:

  1. Setting your AdControl or DrawableAd size to less than the standard or minimum size required to show an ad. For example, if you choose an ad unit size in pubCenter of 320x50 but set the size of the AdControl to 300x50, no add will be shown.

  2. Setting your AdControl or DrawableAd size to Auto.

  3. Using filters that limit the availability of displayable ads.

  4. Using the test values for the ApplicationId and AdUnitId in your live app will not display any ads.

  5. It can take an hour for new ad unit ids created in pubCenter to be available.

If you can see test ads in the Emulator, but do not receive live ads in your app, your code is able to display ads as expected. Contact product support.

Inherited Properties

The following inherited properties are not useable by the AdControl. Do not set their values.

  • BorderThickness

  • BorderBrush

  • Clip

  • OpacityMask

Do Not Remove The AdControl While An Ad Is Expanded

While an ad is expanded, if you remove the AdControl then closing the expanded ad may result in undefined behavior for your app. Check the IsEngaged property before removing the AdControl.

SystemTray Overrides The AdControl Z-Order

If you code your app to show an ad where the SystemTray would appear, the SystemTray will obscure the ad. Regardless of the z-order setting for the AdControl, the SystemTray always takes precedence.

Support and Feedback

Get product support or report a bug in the product by visiting the Windows Phone Dev Center support page (scroll down to the section "Microsoft Advertising support").

Send feedback about this documentation to adsfdbk@microsoft.com. There is no product support through this alias. Documentation feedback only.

Community Additions

© 2015 Microsoft