MoPub
  1. publishers
  2. Android SDK
  3. Android SDK Changelog

Android SDK Changelog

Version 5.7.0 (May 20, 2019)

  • Features
    • Impression Level Revenue Data - a data object that includes revenue information associated with each impression.
    • Verizon Ads SDK now supported as a mediated network.
    • Upgraded Gradle dependency to 5.4.1
    • Upgraded Robolectric dependency to 4.2.1.
    • Upgraded com.android.tools.build:gradle to 3.4.0.
    • Sample app improvements.
  • Bug Fixes
    • Handle empty impression trackers in VAST.
    • Improved impression handling when MoPubView is reattached to the screen.

Version 5.6.0 (March 18, 2019)

  • Features
    • Enabled debug logging when using a debug Google Advertising ID (one that ends with “10ca1ad1abe1”).
    • Upgraded ExoPlayer dependency to 2.9.5.
    • Upgraded MoPub-Volley dependency to 2.1.0.
  • Bug Fixes
    • Banners no longer refresh when they are expanded. They will resume refreshing when the expanded view is closed.
    • Setting orientation on an expanded banner no longer locks the orientation after the expanded view is closed.
    • Improved click detection.
    • Catch MissingWebViewPackageException in ConsentDialogLayoutWebView.
    • Reduce ANRs by removing synchronization from Networking#getUserAgent(Context).

Version 5.5.0 (January 28, 2019)

  • Features
    • Advanced Bidding automatically initializes. See https://developers.mopub.com/publishers/android/initialization/ for more information about initialization.
    • GDPR legitimate interest API now available; publishers may opt into allowing supported networks to collect user information on the basis of legitimate interest.
    • Improved logging from the SDK. Set the log level with SdkConfiguration.Builder#withLogLevel(LogLevel) in initialization to change the logging granularity.
    • Upgraded Gradle dependency to 4.8
    • Upgraded Android Plugin dependency to 3.2.0
  • Bug Fixes
    • Addresses an ANR when requesting an ad immediately after initialization.
    • MRAID isReady is now called after the load is finished instead of when the ad is shown.

Version 5.4.1 (November 28, 2018)

  • Bug Fixes
    • Fixed bug with the internal state of rewarded video when the video fails to play.
    • Fixed bug where initialization complete is called multiple times.
    • Fixed Google Advertising ID fetching logic.
    • Marked gdprApplies as nullable
    • Added cleartextTrafficPermitted=”true” to Android Sample App.
    • Fixed bug where rewardedAdsLoaders.markPlayed() was fired before onRewardedVideoClosed().
    • Added adDidFail callback to !isNetworkAvailable() in AdViewController.

Version 5.4.0 (October 3, 2018)

  • Upgraded target SDK version to 28 and support libraries to 28.0.0.
  • Upgraded ExoPlayer dependency to 2.8.3.
  • Moved AdvancedBiddingInitializationAsyncTask and RefreshAdvertisingInfoAsyncTask to the parallel executor.
  • MRAID isViewable now more closely follows our impression tracking instead of the ad being marked viewable as soon as it loads.
  • Bug fixes.

Version 5.3.0 (August 15, 2018)

  • This release includes the foundation work for SDK to receive optimized responses for multiple placements from the waterfall. This effort will reduce the number of server roundtrips and minimize the ad response latency.
  • Upgraded ExoPlayer dependency to 2.8.2.
  • Upgraded recommended Google Play Services dependency to 15.0.1.
  • Upgraded target sdk version to 27 and support libraries to 27.1.1.
  • Upgraded Gradle dependency to 4.4.
  • Upgraded Android Plugin dependency to 3.1.3.
  • Upgraded test dependencies Powermock to 1.6.6 and Robolectric to 3.8.
  • Bug Fixes.

Version 5.2.0 (July 9, 2018)

  • SDK initialization is required for ads to load. Ad requests will fail unless MoPub is initialized.
  • MoPub#isSdkInitialized() now more accurately reflects whether or not MoPub is initialized. This method now returns true after the SdkInitializationListener#onInitializationFinished() callback instead of immediately.
  • Bug fixes.

Version 5.1.0 (June 5, 2018)

  • Upgraded Moat dependency to 2.4.5.
  • Banners now only refresh after an impression is made.
  • Added PersonalInfoManager.forceGdprApplies() in order to let MoPub know that this app should always apply GDPR rules.
  • Loading MoPub’s consent dialog is only possible when GDPR rules applies to the app.
  • Bug fixes.

Version 5.0.0 (May 14, 2018)

  • General Data Protection Regulation (GDPR) update to support a way for publishers to determine GDPR applicability and to obtain and manage consent from users in European Economic Area, the United Kingdom, or Switzerland to serve personalized ads.
  • New SDK initialization method to initialize consent management and rewarded video ad networks. Required for receiving personalized ads. In future versions of the SDK, initialization will be required to receive ads.
  • Updated network stack to MoPub-Volley-2.0.0.
  • Updated ad requests to use POST instead of GET.
  • All communication with MoPub servers is now made via HTTPS.

Version 4.20.0 (February 20, 2018)

  • Upgraded Gradle dependency to 4.3.1.
  • Upgraded Moat dependency to 2.4.1. This fixes the AAPT2 manifest merge error.
  • Fixed a viewability bug for video ads where ViewGroups were not being properly added to the list of known obstructions.
  • We are formally separating network adapters from our MoPub SDK. This is to enable an independent release cadence resulting in faster updates and certification cycles. New mediation location is accessible here. We have also added an additional tool, making it easy for publishers to get up and running with the mediation integration. Check out https://developers.mopub.com/publishers/mediation/integrate/ and integration instructions at https://developers.mopub.com/publishers/android/integrating-networks/.
  • Bug fixes.

Version 4.19.0 (December 11, 2017)

  • Updated Facebook Audience Network adapters to 4.26.1.
  • Updated Flurry adapters to 8.1.0.
  • Updated Millennial rewarded ads adapters to 6.6.1.
  • Fixed a potential crash for native video ads when attempting to blur the last video frame.
  • Fixed a duplicate on loaded callback for some rewarded ads.

Version 4.18.0 (November 1, 2017)

  • Updated the SDK compile version to 26. Android API 26 artifacts live in the new Google maven repository maven { url 'https://maven.google.com' }. See this article for more information about using Android API 26.
  • Fixed MoPub in-app browser’s back and forward button icons.
  • Updated AdMob adapters to 11.4.0.
  • Updated Chartboost adapters to 7.0.1.
  • Updated Facebook Audience Network adapters to 4.26.0.
  • Updated Millennial to 6.6.1.
  • Updated TapJoy adapters to 11.11.0.
  • Updated Unity Ads adapters to 2.1.1.
  • Updated Vungle adapters to 5.3.0.
  • Bug fixes.

Version 4.17.0 (September 27, 2017)

  • Rewarded Ads can now send up optional custom data through the server completion url. See MoPubRewardedVideos#showRewardedVideo(String, String).
  • Updated Facebook native adapter to ignore clicks on whitespace as per Facebook policy.

Version 4.16.1 (August 24, 2017)

  • Fixed issue where null javascript was being passed to AVID video sessions.

Version 4.16.0 (August 23, 2017)

  • Added support for viewability measurement from IAS (AVID library) and Moat.
    • Important: New dependencies were included in this release; please update your build.gradle’s repositories block to include maven { url "https://s3.amazonaws.com/moat-sdk-builds" }. Note that the AVID library is provided on JCenter, so no additional steps must be taken – it will be included automatically.
    • To disable this feature, see note below on Disabling Viewability Measurement.
  • Interstitials are now loaded offscreen instead of in a separate WebView.
  • Rewarded Videos have a new init method. See MoPubRewardedVideos.initializeRewardedVideo(Activity, List<Class<? extends CustomEventRewardedVideo>>, MediationSettings...). Pass in a list of networks to initialize, and MoPub will initialize those networks with the settings from the previous ad request, persisted across app close.
  • Upgraded our ExoPlayer dependency to 2.4.4.
  • Bug fixes

Disclosures

MoPub v4.16 SDK integrates technology from our partners Integral Ad Science, Inc. (“IAS”) and Moat, Inc. (“Moat”) in order to support viewability measurement and other proprietary reporting that IAS and Moat provide to their advertiser and publisher clients. You have the option to remove or disable this technology by following the opt-out instructions below.

If you do not remove or disable IAS’s and/or Moat’s technology in accordance with these instructions, you agree that IAS’s privacy policy and license and Moat’s privacy policy, terms, and license, respectively, apply to your integration of these partners’ technologies into your application.

Disabling Viewability Measurement

There are a few options for opting out of viewability measurement:

Strip out from JCenter Integration

Normally, to add the MoPub SDK to your app via JCenter, your build.gradle would contain:

dependencies {
  compile('com.mopub:mopub-sdk:4.16.0@aar') {
    transitive = true
  }
}

Update to the following to exclude one or both viewability vendors:

dependencies {
  compile('com.mopub:mopub-sdk:4.16.0@aar') {
    transitive = true
    exclude module: 'libAvid-mopub' // To exclude AVID
    exclude module: 'moat-mobile-app-kit' // To exclude Moat
    }
}
Strip out from GitHub integration

Navigate to the gradle.properties file in your home directory (e.g. ~/.gradle/gradle.properties) and include one or both of these lines to opt out of viewability measurement for AVID and/or Moat.

mopub.avidEnabled=false
mopub.moatEnabled=false
Disable via API

If you would like to opt out of viewability measurement but do not want to modify the MoPub SDK, a function is provided for your convenience. At any point, call MoPub.disableViewability(vendor);. This method can can be called with any of the enum values available in ExternalViewabilitySessionManager.ViewabilityVendor: AVID will disable AVID but leave Moat enabled, MOAT will disable Moat but leave AVID enabled, and ALL will disable all viewability measurement.

Version 4.15.0 (June 19, 2017)

  • The SDK now sends Advertising ID on Amazon devices when appropriate.
  • Fixed issue with Charles proxy in sample app for API 24+.
  • Bug fixes.

Version 4.14.0 (May 10, 2017)

  • Rewarded Ad reward callback onRewardedVideoCompleted(Set<String>, MoPubReward) is also triggered now on the client for server-side rewarding.
  • Added click callback for Rewarded Ads.
    • Any implementors of MoPubRewardedVideoListener will now need to also implement MoPubRewardedVideoListener#onRewardedVideoClicked(String).
  • MoPub Ads now expire after 4 hours of being unused.
    • Interstitial and Rewarded ads served by MoPub will expire 4 hours after successfully loading, triggering a load failure with the new EXPIRED MoPubErrorCode.
    • Cached Native Ad Placer ads now also expire in 4 hours.
  • Improved logging when attempting to show an ad that is not ready.
  • Updated build tools version to 25.0.2.
  • Bug fixes.

Version 4.13.0 (March 23, 2017)

  • Updated AdColony Custom Events.
  • Updated Unity Custom Events.
  • Added AdMob Custom Events:
    • Native: GooglePlayServicesAdRenderer and GooglePlayServicesNative
    • Rewarded Video: GooglePlayServicesRewardedVideo
  • Bug fixes.

Version 4.12.0 (February 9, 2017)

  • Updated minimum supported Android API version to 16+ (Jelly Bean).
  • New required Activity declaration in AndroidManifest, please add:
<activity android:name="com.mopub.mobileads.RewardedMraidActivity"
          android:configChanges="keyboardHidden|orientation|screenSize"/>
  • Added support for rich media in rewarded video inventory.
  • Bug fixes:
    • Fixed incorrectly forwarded lifecycle events onStop() and onDestroy() in MoPubLifeCycleManager for rewarded rich media ads.
    • Prevented MoPub-related crashes due to system-level WebView updates while the app is running.
    • Allow video playback in reverseLandscape orientation (in addition to previously supported landscape orientation).
    • Fixed crash caused by invalid VAST absolute tracker values.

Version 4.11.0 (November 10, 2016)

  • Added a workaround for an Android bug where Lollipop devices (Android 5.1.1, API level 22) and lower incorrectly handle SSL connections using Server Name Identification.
  • Rewarded video load() calls now do not load another rewarded video with the same ad unit id while one is already loading or loaded.
  • Moved the VAST video start tracker to immediately after the video starts (was 2 seconds after the video started).
  • Bug fixes.

Version 4.10.0 (October 18, 2016)

  • Added and updated mediated network versions
    • Added Flurry version 6.5.0. All Flurry adapters can be found in the corresponding extras directory (/extras/src/com/mopub/mobileads for banners and interstitials, /extras/src/com/mopub/nativeads for native).
      • All Flurry ad formats must include: FlurryAgentWrapper
      • Banners: FlurryCustomEventBanner
      • Interstitial: FlurryCustomEventInterstitial
      • Native: FlurryCustomEventNative, FlurryBaseNativeAd, FlurryNativeAdRenderer, and FlurryViewBinder
    • Certified Facebook Audience Network version 4.15.0
    • Certified Tapjoy version 11.8.2
    • Certified Millennial Media version 6.3.0
    • Certified Vungle version 4.0.2
  • Fixed intermittent IllegalStateException for MRAID creatives attemping to retrieve getRootView() on unattached Views.
  • Updated mopub-sample’s example proguard.cfg to properly retain methods called only via reflection.

Version 4.9.0 (September 1, 2016)

  • Removed the full SDK bundle.
  • Removed Eclipse support.
  • Removed InMobi custom events from extras.
  • Deprecated rewarded video calls from MoPub.java and moved them to MoPubRewardedVideos.java.
    • For example, MoPub#loadRewardedVideo is deprecated in favor of MoPubRewardedVideos#loadRewardedVideo.
  • Bug fixes.

Modular SDK

  • Added the ability to specify which ad formats to include as dependencies (to decrease the overall footprint of the MoPub SDK in your app).
  • Default behavior remains unchanged and includes access to all ad formats.
  • Note: Maven builds from source are currently unstable and will be reinstated in a future release. Maven developers can still pull the MoPub SDK AAR from JCenter.

Version 4.8.0 (August 1, 2016)

  • Changed the behavior of MoPubInterstitial#load() while an interstitial is loading or has been successfully loaded. Previously, this would discard the currently-caching or cached interstitial – now the interstitial will be unaffected and will remain in the cache.
  • MoPubInterstitials can now be shown only once per successful ad load.
  • Modified a number of Native Ads APIs (manual integration) to accept Context instead of Activity. Affected classes/methods include: MoPubNative, AdapterHelper, CustomEventNative#loadNativeAd(), and MoPubAdRenderer#createAdView().

Version 4.7.1 (June 10, 2016)

  • Fixed deeplink bug.

Version 4.7.0 (June 2, 2016)

  • Rewarded video server-side currency rewarding (Beta).
  • Enhanced Android intent handling.

Version 4.6.1 (May 5, 2016)

  • Enhanced caching logic for HTML and MRAID interstitials. Resource-heavy interstitials will now render more quickly when MoPubInterstitial#show() is called.

Version 4.6.0 (April 21, 2016)

  • Certified Chartboost version 6.4.1
  • Certified Tapjoy version 11.5.1

Version 4.5.1 (March 31, 2016)

  • Updated ExoPlayer dependency from r1.4.2 to r1.5.6; courtesy @talklittle. Removed references to READ_EXTERNAL_STORAGE permission.

Version 4.5.0 (March 24, 2016)

  • Rewarded video support from the MoPub Marketplace (Beta)
  • Miscellaneous bug fixes.

Version 4.4.1 (February 23, 2016)

  • Fixed deeplink bug where host must be present in URL.

Version 4.4.0 (February 11, 2016)

  • Updated permission model to be compatible with Android 6.0 (API level 23).
  • Enhancements and bug fixes for video ads.

Version 4.3.0 (December 15, 2015)

  • Enhancements and bug fixes for VAST video ads.

Version 4.2.0 (November 30, 2015)

  • Support for mediating Facebook Native Video ads.
  • Mediated Facebook Native Ads now display the AdChoices icon.
  • Support for Facebook SDK 4.8.1

Version 4.1.0 (November 12, 2015)

  • A number of Native Ad classes now require Activity instances instead of Context. Most users should be unaffected by this change, and it fixes a crash caused by handling themes incorrectly. The following classes are affected:

    • CustomEventNative and its implementations including MoPubCustomEventNative.
    • MoPubAdAdapter and MoPubRecyclerAdapter.
    • MoPubAdRenderer and its implementations.
    • MoPubStreamAdPlacer
    • MoPubNative
    • NativeAd and NativeAdSource
    • NativeAdViewHelper
  • Vungle’s ad adapters have been updated for their 3.3.0 SDK.
  • Tapjoy adapters for interstitials and rewarded video are included for their 11.2.2 SDK.
  • The Play Services adapters have been tested with Play Services 7.8.0.

Version 4.0.0 (October 6, 2015)

Version 4.0.0 includes a number of improvements to our Native Ads systems under the hood. This means a few changes for publishers integrating the ads. The Native Ads Integration Guide describes all the steps you’ll need to integrate 4.0.0.

Native Ads Changes

  • MoPubNativeAdRenderer has been replaced by MoPubStaticNativeRenderer
  • When requesting ads using MoPubNative, you must instantiate and register a MoPubStaticNativeAdRenderer. See the Integration Document for more details.
  • NativeResponse has been replaced with NativeAd
  • NativeAd has a new API that supports creating and rendering Views for Native Ads.
    • #createAdView returns a View that can hold data for the NativeAd
    • #renderAdView will populate the View with ad data.
    • Other lifecycle methods from NativeResponse remain:
      • #prepare, #clear, #destroy
  • The process of writing new CustomEventNative instances has changed. These changes will support more dynamic, flexible, and attractive Native Ad formats in the future. All bundled native Custom Event files have been updated to use the new API.

Removed Old Code

  • Removed legacy banner/interestitial listeners, deprecated in 1.11
  • Removed legacy custom event implementation (“custom event methods”) deprecated in 1.10

Version 3.13.0 (September 21, 2015)

  • Android M Support - Replaced usage of the now-deprecated HttpClient with HttpURLConnection.

Version 3.12.0 (August 31, 2015)

  • Rewarded Video Mediation is now Generally Available. We provide support for Unity Ads, Chartboost, Vungle, and Ad Colony rewarded video.
  • Privacy Information Icon is now available for native ads. You should add this view to your ViewBinder. See the example in the MoPub Sample app.

Version 3.11.0 (August 20, 2015)

  • Updated Millennial Media support to 6.0.0, including updates to the MillennialBanner.java and MillennialInterstitial.java custom events.
  • Added mediation for Millennial Media native ads: MillennialNative.java, located in the native extras directory of the SDK (/extras/src/com/mopub/nativeads).

Version 3.10.0 (August 3, 2015)

  • VAST UI improvements and bug fixes.
    • Pause trackers no longer fire when the ad is skipped.
    • Improved retrieval of blurred video frame when there is no companion ad.
  • Added com.mopub:mopub-sdk AAR to jCenter.
  • Bug Fixes:
    • Fixed a NullPointerException in CacheService on devices with low storage space.
    • Improved redirect loading for in-app browser.

Version 3.9.0 (July 1, 2015)

  • Added VAST 3.0 standard support for video ads.
  • Improved video player UX.
  • Added RecyclerView support for native ads. See the integration guide.
  • Improved deep link handling.
  • Bug Fixes:
    • MRAID video interstitials now play automatically when displayed on Jellybean MR1 and newer.
    • MRAID relative assets are correctly rendered.
    • MoPubLog no longer duplicates some messages.
    • Fixed erroneous output of DeviceUtils.getScreenOrientationFromRotationAndOrientation().

Version 3.8.0 (June 1, 2015)

  • Updated Chartboost support to 5.3.0. This introduces a new shared class called ChartboostShared. If you are using Chartboost Custom Native Networks you will need to include this class in your build along with ChartboostInterstitial.

Version 3.7.0 (April 30, 2015)

  • Updated GooglePlayServices custom events to depend on the Google Play Services play-services-ads 7.0.0 API.
  • Vungle support updated to SDK 3.3.3.
  • Updated InMobi and Greystripe custom events to accept application IDs from the MoPub UI.
    • For InMobi: {"app_id" : "YOUR_INMOBI_APP_ID"}
    • For Greystripe: {"GUID" : "YOUR GREYSTRIPE_GUID"}
  • Added toasts to the MoPub Sample App for ad load failures due to no connection.
  • Fixed a bug in processing VAST progress trackers in a VAST wrapper tag.

  • Fixed a bug where ad refresh times could be incorrect when an ad request was not filled.

  • Updated the following dependencies:
    • support-v4 AAR to 22.0.0
    • support-annotations JAR to 22.0.0
    • Android Maven Plugin to 4.2.0

Version 3.6.1 (April 6, 2015)

  • Bug Fix Fixed a compile error in FacebookBanner.java

Version 3.6.0 (April 3, 2015)

  • Facebook Update Updated supported Facebook Audience Network version to 3.23.1
  • Bug fix Fixed a bug where interstitials could leak memory
  • VAST Video Updated the VAST video player to support Progress events.
  • Updated Volley version to 1.1.0.

Version 3.5.0 (March 10, 2015)

  • Dependency changes in Maven and Gradle. No new dependencies have been added, but your build script will need to change slightly to include JCenter. See our Getting Started Guide for complete instructions.
  • Security Improvement: removed the @JavascriptInterface annotation for WebViews.
  • Fixed a bug where video playback would sometimes fail to stop when an ad was dismissed.
  • Fixed a bug where it was not possible to disable ad refresh
  • Fixed a null pointer exception in AdViewController

Version 3.4.0 (January 30, 2015)

  • Volley networking stack MoPub for Android now uses Google’s Volley library for HTTP requests. You will need to add our bundled Volley JAR (available at mopub-sdk/libs/mopub-volley-1.0.0.jar) as a compile-time dependency. See instructions in our integration page.
  • Updated Vungle Support Certified the VungleInterstitial custom event against Vungle SDK 3.2.2
  • VAST Video Bug Fixes
    • Fixed inability to parse VAST tags referencing URLs that contain 3rd party macros
    • VAST videos no longer fire completion trackers upon video playback error
  • Added support for the mopubnativebrowser:// click-destination scheme for Native, MRAID, and VAST ads (it was already supported for HTML ads). Links of this type (e.g. mopubnativebrowser://navigate?url=https%3A%2F%2Fwww.mopub.com) will open the specified URL in the device’s default browser, rather than in MoPub’s in-app browser.

Version 3.3.0 (December 8, 2014)

  • MRAID 2.0 Support - The MoPub SDK is now compliant with the MRAID 2.0 specification to enable rich media ads in banners and interstitial ad units. Learn more about MRAID from the IAB.

  • Location Polling Updates - Changed the interaction between application- and device-provided location data: more recent location data is now always used (in the past, application-provided location data was always preferred).

    As before, you may still disable MoPub SDK’s location polling by calling MoPub.setLocationAwareness(LocationAwareness.DISABLED).

  • Updated Chartboost SDK Updated the ChartboostInterstitial custom event to support Chartboost SDK 5.0.4
  • Android Support Annotations Introduced a dependency on android-support-annotations.jar to support code analysis of @Nullable and @NonNull annotations.

Version 3.2.2 (October 29, 2014)

  • Bug Fix Fixes a bug in fetching the Google Advertising ID from Google Play Services.

Version 3.2.1 (October 21, 2014)

  • Bug Fix Fixes a bug in processing certain HTTP headers for Native Ads.

Version 3.2.0 (October 17, 2014)

Version 3.1.0 (October 9, 2014)

  • Updated Facebook SDK Compatibility to 3.18.1 Provided Custom Events for Facebook Banners, Interstitials and Native Ads (included in the extras/ folder) are now compatible with the latest SDK release from Facebook (3.18.1).
  • Updated API for Native Ads Custom Event writers If you are mediating Facebook or InMobi native ads, this change requires you to copy FacebookNative.java and InMobiNative.java custom events from the extras/ folder to com.mopub.nativeads package for compatibility.

Version 3.0.0 (September 30, 2014)

  • Location Settings are now SDK-wide
    • Calls to MoPubView#setLocationAwareness and MoPubInterstial#setLocationAwareness are deprecated in favor of MoPub#setLocationAwareness
    • Calls to MoPubView#setLocationPrecision and MoPubInterstitial#setLocationPrecision are deprecated in favor of MoPub#setLocationPrecision
    • Calls to any of these methods have the effect of setting location awareness and precision globally for the SDK
  • Build target SDK is now API Level 19. If you are building the MoPub SDK from source, modify your dependencies to reference Android 4.4.2, API Level 19. This does not affect the minimum device API level, which remains at API Level 9.
  • Source-level support for Gradle projects. The SDK source now includes a build.gradle file you can use to build source as part of your Gradle project.
  • The SDK now uses Play Services 5.0.89
  • Bug fixes:
    • Millennial Interstitial caching now properly handles request failures
    • Fixed bug preventing native ads from loading after a request failure

Version 2.4.0 (August 28, 2014)

  • Minimum Android version now at API Level 9. To use the new SDK, your app must run on Android 2.3.1 (Version 9, Gingerbread) or higher.
  • Simplified APIs for inserting native ads. See Native Ads Integration for details.
  • Automatic ad caching for smooth scrolling. For native ads, the SDK will now automatically pre-load ads, resulting in smoother scrolling.
  • Performance improvements The SDK now makes more efficient use of memory for image caching and avoids allocating temporary objects while scrolling, resulting in fewer garbage collections.
  • Sample app improvements. An improved sample app allows saving ad unit IDs for testing.
  • Bug fixes:
    • Banner auto-refresh is now properly re-enabled when resuming your app.

Version 2.3 (July 17, 2014)

  • Improved impression tracking for Native Ads Impression tracking for native ads is now more accurate and more efficient.
  • Streamlined Maven Build and Dependencies MoPub’s Android SDK now depends on the Android v4 Support Library shipped with the Android Build tools. The MoPub Sample App also depends on Google Play Services to use the Android Advertising ID. We recommend building against Play Services in your app as well. For integration instructions, see the wiki.
  • Removed AdMob Custom Events and JAR AdMob’s SDK is deprecated by Google and the APIs have been moved to Google Play Services. Existing AdMob adunits will now invoke the appropriate Google Play Services custom event. Developers must update their integration to use the Google Play Services custom events located in the extras folder by August 1.
  • Updated Third-Party Network Compatibility MoPub’s provided Custom Events (included in the extras/ folder) are now compatible with the latest SDK releases from Millennial Media (5.3.0), Vungle (3.1.0), InMobi (4.4.1) and Google Play Services (5.0.77).
  • Fixed intermittent NullPointerException in MoPubNative#requestNativeAd
  • Fixed an issue where MRAID interstitials could be not be closed.

Version 2.2 (June 19, 2014)

  • Native ads mediation release; integration instructions and documentation are available on the GitHub wiki. Added custom event native implementations to the native extras directory of the SDK (/extras/src/com/mopub/nativeads), with initial support for the following networks: - Facebook Audience Network (FacebookNative.java) - InMobi Native Ads (InMobiNative.java)
  • Native ads content filtering: Added the ability to specify which native ad elements you want to receive from the MoPub Marketplace to optimize bandwidth use and download only required assets, via RequestParameters.Builder#desiredAssets(…). This feature only works for the six standard Marketplace assets, found in RequestParameters.NativeAdAsset. Any additional elements added in direct sold ads will always be sent down in the extras.
  • Added star rating information to the NativeResponse object, via NativeResponse#getStarRating(). This method returns a Double corresponding to an app’s rating on a 5-star scale.
  • VAST video quartile and completion trackers now always include the user-agent
  • Ensured that banners never autorefresh until they have been loaded at least once

Version 2.1 (May 15, 2014)

  • Added custom events for Facebook ads. FacebookBanner and FacebookInterstitial can be found in the extras directory of the SDK (/extras/src/com/mopub/mobileads). For more information, please see the help page for Facebook custom events.
  • Significant improvements to video ads
    • Added overlay including a “Learn More” button, video length, and time left until the video may be skipped
    • Added support for companion banners (shown upon video completion)
  • Added Logcat warnings (and Toasts for debug builds) in cases where all necessary Activity permissions haven’t been added to the AndroidManifest

Version 2.0.1 (April 30, 2014)

  • Fixed cases where VAST Video Interstitials were failing to fire InterstitialAdListener callbacks
  • Simplified click tracking logic for HTML ads

Version 2.0 (April 22, 2014)

  • Native Ads public release; integration instructions and documentation available on the GitHub wiki
  • Changed minimum supported Android version to Froyo (Android 2.2, API level 8)
  • Added support for Google Play Services advertising identifier
  • Renamed the com.mopub.mobileads.MraidBrowser Activity to com.mopub.common.MoPubBrowser.
    • Important Note: This change requires a modification to the AndroidManifest. The updated set of requisite activity permissions are as follows:
    ``` 
    ```
  • Upgraded the bundled android-support-v4 library to r19.1.
    • Note for Maven users: Newer versions of the android-support-v4 artifact are unavailable on Maven central, so we have included a small script to update the version in your local artifact repository. Please navigate to the mopub-sdk directory, and run scripts/mavenize_support_library.

Version 1.17.3.1 (March 24, 2014)

  • Restricted use of methods and fields that require API 4+ (WebView#removeJavascriptInterface and ConnectivityManager’s connection types)

Version 1.17.3 (March 19, 2014)

  • Added safeguards to prevent two different MoPubInterstitial objects from listening in on one other’s lifecycle callbacks
  • Disabled Javascript loading into destroy()ed WebViews
  • Fixed an IllegalArgumentException resulting from VAST videos with malformed redirect tags
  • MRAID ads that utilize mraid.open() now correctly record a click event
  • Added missing FLAG_ACTIVITY_NEW_TASK to VastVideoView’s intent creation

Version 1.17.2 (February 20, 2014)

  • Updated InMobi custom events to support InMobi SDK 4.0.3+ only
  • MRAID viewable property now correctly updates on viewability change
  • MraidView properly handles null schemes
  • Internal disk LRU cache correctly hashes keys when checking for existing files

Version 1.17.1.1 (February 5, 2014)

  • Fixed bug that caused clicks to not be recorded in the MoPub UI (introduced in 1.17.1)

Version 1.17.1 (January 23, 2014)

  • Added custom events for Google Play Services. GooglePlayServicesBanner and GooglePlayServicesInterstitial can be found in the extras directory of the SDK (/extras/src/com/mopub/mobileads)
  • Resolved issues with missing annotations on addJavascriptInterface when targetSdkVersion is set to API level 17 or above
  • Updated MoPub sample application to allow in-app text entry of ad unit IDs

Version 1.17 (Nov 20, 2013)

  • Support for VAST 2.0 video playback via MoPub Marketplace
    • Short videos (less than 15 seconds) autoplay and and are unskippable
    • Longer videos autoplay and are skippable after 5 seconds
    • Note: The video cache can use up to 100 MB of internal storage. For developers sensitive to storage constraints, this value may be changed in VastVideoInterstitial.CACHE_MAX_SIZE.
  • Updated InMobi custom event support to 4.0.0
  • Added custom events for video ad network mediation, which can be found in the extras directory of the SDK (/extras/src/com/mopub/mobileads/)
    • Added the AdColonyInterstitial custom event
    • Added the VungleInterstitial custom event
    • Note: Virtual currency callbacks (v4vc) are not supported for the above ad networks
  • Enabled deeplinking via custom URIs in ad creatives
  • All WebViews are removed from their parents before destroy()
  • Removed previously-deprecated HTML5AdView

Version 1.16 (October 16, 2013)

  • Improved creative controls
    • Creative flagging
      • Allows users to report certain inappropriate ad experiences directly to MoPub with a special gesture
      • User must swipe back and forth at least four times in the ad view to flag a creative
      • Swipes must cover more than 1/3 of the ad width and should be completely horizontal
      • Only enabled for direct sold, Marketplace, and server-to-server networks ads
    • Creatives that attempt to auto-redirect are now blocked; ads cannot redirect without user interaction
    • Javascript alert, confirm, and prompt dialogs are blocked
  • Improved responsiveness of showInterstitial() for HtmlInterstitials and MraidInterstitials by pre-rendering HTML content
  • Simplified internal construction and handling of WebViews by removing WebViewPool and its subclasses
  • Updated mraid.getVersion() to return 2.0

Version 1.15.2.2 (September 20, 2013)

  • Removed WebSettings.setPluginsEnabled() so the SDK builds against Android API 18
  • AdMob banners are now removed from the view hierarchy before they are destroyed
  • Prevent ads from launching system features, such as a browser view, until the user has interacted with the ad.

Version 1.15.2.1 (September 13, 2013)

  • Made the SDK more resilient to creatives that improperly use the mopubnativebrowser:// scheme

Version 1.15.2 (September 11, 2013)

  • Allowed Facebook Support to be disabled optionally with setFacebookSupported(false): - Use MoPubInterstitial.setFacebookSupported(false); for interstitials - Use MoPubView.setFacebookSupported(false); for banners - Note: the setFacebookSupported(false) method call must come before loadAd() - Note: facebook support is on by default
  • Changed banner refresh default to be 60 seconds when requests timed out
  • Fixed edge case in Millennial Media ad fetch failure when there is no inventory
  • Fixed a bug where redirect URLs were malformed, causing the native browser to not render ads
  • Updated Millennial Media jar to 5.1.0
  • Updated Greystripe custom event support to 2.3.0
  • Fixed MRAID 2.0 storePicture command’s messaging when a picture either fails to download or fails to save to device
  • Expanded MRAID 2.0 createCalendarEvent command to support both minute- and second-level granularity

Version 1.15.1.1 (September 4, 2013)

  • Made the SDK more resilient to unexpected Flash creatives

Version 1.15.1 (August 27, 2013)

  • Updated documentation to remove the requirement for certain AndroidManifest permissions
  • Fixed minor bug with MRAID 2.0 storePicture command where the user sees a false download completed message

Version 1.15 (August 21, 2013)

Includes support for ads in the MRAID 2.0 format. MRAID 2.0 allows advertisers to create ads with rich media functionality, including adding calendar events, storing pictures and playing videos in the native video player. To learn more about MRAID 2.0, read our help article.

  • Added the following MRAID 2.0 features: createCalendarEvent (Android 4.0 and above), playVideo, storePicture, and supports
  • Hardware Acceleration is now enabled by default for MraidInterstitials on Android 4.0 and above
  • Ensured that Cursors in FacebookKeywordProvider are always closed properly
  • Added tracking parameter to InMobi ad requests
  • Banner WebViews are now removed from the view hierarchy before they are destroyed

To correctly display ads that ask the user to save a picture (storePicture ads), you need to make the following change to AndroidManifest.xml:

  • Add theWRITE_EXTERNAL_STORAGE permission. Note: Adding the permission is optional. If the permission is not added, we will not deliver any store picture ads to the users’ devices. All other features will remain functional without the new permission.

To allow users to play videos using the native video player:

  • Declare activity com.mopub.mobileads.MraidVideoPlayerActivity. This activity is required to support playing videos in the native player and we strongly recommend adding it.

Version 1.14.1 (June 21, 2013)

  • Wait until after loaded interstitials are shown to report an impression
  • Remove phantom impression tracking from interstitials
  • Remove extra whitespace from Millennial banner ads
  • Added onInterstitialClicked() notification to InterstitialAdListener
  • Provide default implementations for BannerAdListener and InterstitialAdListener

Version 1.14 (May 28, 2013)

  • Provided improved support for Android Unity by moving all project resources (including layouts, javascript, images, and values) into source
  • Removed reference to TYPE_DUMMY in AdUrlGenerator because it is not available in earlier versions of Android
  • Fixed NPE in AdUrlGenerator when WiFi is off and Airplane mode is on
  • MraidInterstitials now properly notify InterstitialAdListener when they are shown and dismissed

Version 1.13.1 (May 21, 2013)

  • Updated Millennial support to Millennial Media SDK version 5.0.1

Version 1.13.0.2 (May 17, 2013)

  • Relaxed access modifiers for CustomEventBanner and CustomEventInterstitial

Version 1.13.0.1 (May 15, 2013)

  • Removed extraneous display call in MillennialInterstitial custom event
  • Fixed potential NPE in AdView’s loadUrl()
  • Deprecated HTML5AdView after fixing some compilation issues

Version 1.13 (May 9, 2013)

  • Moved all Android code and documentation to its own repository: mopub-android-sdk
  • Updated Millennial support to Millennial Media SDK version 5.0
    • Support for Millennial Media SDK 5.0.1 is ready and will be released when the new Milllennial SDK becomes available
  • Added GoogleAdMobBanner, GoogleAdMobInterstitial, MillennialBanner, and MillennialInterstitial custom event classes
  • Removed obsolete native network adapters
  • Added timeout for third-party networks (10 seconds for banners and 30 seconds for interstitials)
  • Added more data signals (application version, connection type, and location accuracy)

Version 1.12 (April 26, 2013)

  • Chartboost custom event now automatically parses server data
  • Added support for Millennial Media SDK 5.0
  • Initial support for data signals (connectivity and carrier)

Version 1.11 (March 13, 2013)

  • Deprecated multiple MoPubView event listener interfaces in favor of a unified MoPubView.BannerAdListener interface
  • Deprecated MoPubInterstitial listener interface in favor of a new MoPubInterstitial.InterstitialAdListener interface
  • Added “shown” and “dismissed” listener methods to MoPubInterstitial.InterstitialAdListener interface
  • Fixed a NullPointerException in MoPubInterstitial for waterfalls containing multiple custom events
  • Fixed a NullPointerException when tracking impressions for native network SDKs
  • Fixed issue causing MoPubView to left-align HTML banners
  • Fixed issue causing incorrect return value for isReady when using MoPubInterstitial and custom events

Version 1.10 (February 13, 2013)

  • Introduced custom event classes
  • Improved error logging during AdFetch
  • Fixed view resource ID conflicts in MraidDisplayController
  • Fixed issue in which un-implemented custom events could disrupt the mediation waterfall
  • Added ability to force refresh ad units
  • Added testing accessors to MoPubView and MoPubInterstitial
  • Updated to correctly reflect MRAID capabilities in ad request
  • Updated to perform HttpClient shutdown on background thread

Version 1.9 (September 27, 2012)

  • Added support for the Facebook ads test program
  • Updated the Millennial adapters to support SDK version 4.6.0

Version 1.8 (September 6, 2012)

  • Fixed a crash resulting from following market:// links when Google Play is not installed
  • Added in-app browser support for more Google Play redirect styles
  • Added exponential backoff on ad server failure
  • Included new ad unit IDs for sample ads in SimpleAdsDemo
  • Removed extraneous image files

Version 1.7 (August 2, 2012)

  • Added support for Millennial Media leaderboard ads

Version 1.6 (June 29, 2012)

  • Improved click experience by directing clicks to an in-app browser
  • Fixed errors loading mraid.js from disk on Android 4.0+
  • Added ThreadPoolExecutor for AsyncTasks on Android 4.0+
  • Fixed incorrect failover behavior for Custom Native Network banners

Version 1.5 (May 10, 2012)

  • Added support for Millennial Media SDK 4.5.5
  • Fixed ANR relating to synchronization in LoadUrlTask
  • Fixed IllegalArgumentExceptions when creating HttpGet objects with malformed URLs

Version 1.4 (March 28, 2012)

  • Fixed some NullPointerExceptions in the AdMob and Millennial native adapters
  • Fixed issues in which third-party adapters might not properly fail over
  • Fixed a crash caused by unregistering non-existent broadcast receivers

Version 1.3 (March 14, 2012)

  • Fixed handling of potential SecurityExceptions from network connectivity checks
  • Exposed keyword APIs for interstitials
  • Fixed click-tracking for custom:// and other non-http intents

Version 1.2 (February 29, 2012)

  • Added support for custom events
  • Added network connectivity check before loading an ad
  • Added OnAdPresentedOverlay listener methods

Last updated May 20, 2019

TWITTER, MOPUB, and the Bird logo are trademarks of Twitter, Inc. or its affiliates. All third party logos and trademarks included are the property of their respective owners.

© 2019 MoPub (a division of Twitter, Inc.)