Step 1. Add the JitPack repository to your build file
Add it in your root settings.gradle at the end of repositories:
dependencyResolutionManagement {
repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
repositories {
mavenCentral()
maven { url 'https://jitpack.io' }
}
}
Add it in your settings.gradle.kts at the end of repositories:
dependencyResolutionManagement {
repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
repositories {
mavenCentral()
maven { url = uri("https://jitpack.io") }
}
}
Add to pom.xml
<repositories>
<repository>
<id>jitpack.io</id>
<url>https://jitpack.io</url>
</repository>
</repositories>
Add it in your build.sbt at the end of resolvers:
resolvers += "jitpack" at "https://jitpack.io"
Add it in your project.clj at the end of repositories:
:repositories [["jitpack" "https://jitpack.io"]]
Step 2. Add the dependency
dependencies {
implementation 'com.github.adxcorp:mopub-android-sdk:5.18.0.2'
}
dependencies {
implementation("com.github.adxcorp:mopub-android-sdk:5.18.0.2")
}
<dependency>
<groupId>com.github.adxcorp</groupId>
<artifactId>mopub-android-sdk</artifactId>
<version>5.18.0.2</version>
</dependency>
libraryDependencies += "com.github.adxcorp" % "mopub-android-sdk" % "5.18.0.2"
:dependencies [[com.github.adxcorp/mopub-android-sdk "5.18.0.2"]]
Thanks for taking a look at MoPub! We take pride in having an easy-to-use, flexible monetization solution that works across multiple platforms.
Sign up for an account at http://app.mopub.com/.
You can find integration documentation on our wiki and additional help documentation on our developer help site.
To file an issue with our team visit the MoPub Forum or email support@mopub.com.
Thank you for submitting pull requests to the MoPub Android GitHub repository. Our team regularly monitors and investigates all submissions for inclusion in our official SDK releases. Please note that MoPub does not directly merge these pull requests at this time. Please reach out to your account team or support@mopub.com if you have further questions.
The MoPub SDK is available via:
Maven Central Repository
The MoPub SDK is available as an AAR via Maven Central; to use it, add the following to your build.gradle
.
repositories {
mavenCentral() // includes the MoPub SDK
google() // necessary for Android API
}
dependencies {
implementation('com.mopub:mopub-sdk:5.18.0@aar') {
transitive = true
}
}
SDK Modularization
With the modular SDK, you can choose to include specific formats to decrease overall SDK footprint in your app. To do so, include the line for any combination of components that you want in your build.gradle
file as follows:
repositories {
// ... other project repositories
mavenCentral() // includes the MoPub SDK
google() // necessary for Android API
}
dependencies {
// ... other project dependencies
// For banners
implementation('com.mopub:mopub-sdk-banner:5.18.0@aar') {
transitive = true
}
// For interstitials and rewarded ads
implementation('com.mopub:mopub-sdk-fullscreen:5.18.0@aar') {
transitive = true
}
// For native static (images).
implementation('com.mopub:mopub-sdk-native-static:5.18.0@aar') {
transitive = true
}
}
To continue integration using the mopub-sdk AAR, please see the Getting Started guide.
Zipped Source
The MoPub SDK is also distributed as zipped source code that you can include in your application:
MoPub Android SDK.zip
Includes everything you need to serve MoPub ads. No third party ad networks are included.
For additional integration instructions, please see the Getting Started guide.
Cloned GitHub repository
Alternatively, you can obtain the MoPub SDK source by cloning the git repository:
git clone git://github.com/mopub/mopub-android-sdk.git
For additional integration instructions, please see the Getting Started guide.
Please view the changelog for a complete list of additions, fixes, and enhancements in the latest release.
Features
Bug Fixes
MoPubInline
caused by InteractionListener
OutOfMemoryError
crash.If you are integrating with v5.6.0 or later of the MoPub SDK, specify the sourceCompatibility
and targetCompatibility
as below to prevent compilation errors with ExoPlayer 2.9.5 and later:
android {
compileOptions {
sourceCompatibility JavaVersion.VERSION_1_7
targetCompatibility JavaVersion.VERSION_1_8
}
}
AVID and Moat have been removed as MoPub works on a future viewability solution. No action is necessary, though the maven repository for Moat is no longer required. All supported network adapters have been updated and are not backwards compatible. Please update to the latest network adapters when upgrading to SDK 5.13.0.
Please see the Getting Started Guide for instructions on upgrading from SDK 4.X to SDK 5.0.
For GDPR-specific upgrading instructions, also see the GDPR Integration Guide.
If your app's target SDK is 23 or higher and the user's device is running Android 6.0 or higher, you are responsible for supporting runtime permissions, one of the changes introduced in Android 6.0 (API level 23). In addition to listing any dangerous permissions your app needs in the manifest, your app also has to explicitly request the dangerous permission(s) during runtime by calling method requestPermissions()
in the ActivityCompat
class.
ACCESS_COARSE_LOCATION
is needed to pass network location data to MoPub.ACCESS_FINE_LOCATION
is needed to pass GPS location data to MoPub.
ACCESS_FINE_LOCATION
also allows network location data to be passed to MoPub without the need to also grant ACCESS_COARSE_LOCATION
.WRITE_EXTERNAL_STORAGE
.To view the full license, visit http://www.mopub.com/legal/sdk-license-agreement/.
We have partnered with the IAB to provide Viewability measurement via the Open Measurement SDK as of version 5.14.0. To view the full license, visit https://www.mopub.com/en/omlv1