Integrate Vungle SDK for Android or Amazon

Before You Begin


  • The integration requires a Vungle account, so create a Vungle account if you haven’t already done so, and create a new Android or Amazon app in your account. Refer to the Add Your Apps and Placements section of our Using the Publisher Dashboard article to learn how to set up placements in the Vungle dashboard.
  • Android 4.0 (Ice Cream Sandwich - API version 14 or higher)
  • Amazon OS 5.4 or higher
  • MREC and banner ads require API version 16 or higher
  • Migrated to AndroidX on Android SDK 6.5.1

Download the SDK

Download the Vungle SDK for Android or Amazon here:

Reference: Sample App and Java Doc

Step 1. Include the Vungle SDK in Your Project

You can integrate the Vungle SDK either as a Gradle dependency, or manually using a JAR integration.

Option 1. Gradle Integration

Open the project-level build.gradle, and ensure that the JCenter details are as shown here:

allprojects {
  repositories {

Open the app-level build.gradle file for your app, and add compile dependencies in the dependencies section.

buildscript {
  repositories {

dependencies { 
  // Vungle SDK
  implementation 'com.vungle:publisher-sdk-android:6.5.3'
  implementation "androidx.core:core:1.1.0"
  implementation "androidx.localbroadcastmanager:localbroadcastmanager:1.0.0"

  // When appcompat is being used, core and localbroadcastmanager are the dependencies
  // that is getting included
  // implementation 'androidx.appcompat:appcompat:1.1.0'

  // Recommended for SDK to be able to get Android Advertising ID
  implementation ''
  implementation ''

If you include the Vungle SDK as a Gradle dependency, skip ahead to "Step 2. Import the Vungle SDK."

Option 2. Manual JAR/AAR Integration

  1. Download the Vungle SDK v. 6.5.3 and unzip it. From the libs folder, copy all the .jar files, and add them to your project libs folder:
    • vungle-android-sdk-6.5.3.jar
    • converter-gson-2.5.0.jar
    • gson-2.8.2.jar
    • logging-interceptor-3.12.0.jar
    • okhttp-3.12.0.jar
    • okio-1.15.0.jar
    • retrofit-2.5.0.jar
    • androidx-vng-moat-mobile-app-kit-2.6.3.jar

    This zip file contains the SDK both as a .jar file and as an .aar file. Use only one of these, depending on whether you are performing a JAR or an AAR integration.

    If you are performing a remote JCenter Gradle integration, you don't need this zip file and its contents.
  2. Open the project-level build.gradle, and update the repositories section:
    allprojects {
    repositories {
  3. Open the app-level build.gradle file for your app, and add other dependencies in the dependencies section.

    If you are using .aar instead of .jar, you do not need to include VNG-moat-mobile-app-kit-2.6.3.jar, because .aar is already packaged with this library.
    dependencies {
      // Vungle SDK
      implementation files('libs/vungle-android-sdk-6.5.3.jar')
      // Required Third-party Dependencies
      implementation files('libs/converter-gson-2.5.0.jar')
      implementation files('libs/gson-2.8.2.jar')
      implementation files('libs/logging-interceptor-3.12.0.jar')
      implementation files('libs/okhttp-3.12.0.jar')
      implementation files('libs/okio-1.15.0.jar')
      implementation files('libs/retrofit-2.5.0.jar')
      implementation files('libs/androidx-vng-moat-mobile-app-kit-2.6.3.jar') // Exclude when using AAR
      implementation "androidx.core:core:1.1.0"
      implementation "androidx.localbroadcastmanager:localbroadcastmanager:1.0.0"
      // When appcompat is being used, core and localbroadcastmanager are the dependencies
      // that is getting included
      // implementation 'androidx.appcompat:appcompat:1.1.0'
      // Recommended for SDK to be able to get Android Advertising ID
      implementation ''
      implementation ''
  4. Update AndroidManifest.xml by adding the following lines to your AndroidManifest.xml and assigning the application item name to your application class name for MultiDex:
    <!--Required Permissions-->
    <uses-permission android:name="android.permission.INTERNET" />
    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
    <!--Recommended Permissions-->
    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" android:maxSdkVersion="18" />
    <!--Vungle Activities-->
        android:theme="@android:style/Theme.NoTitleBar.Fullscreen" />
        android:theme="@android:style/Theme.Translucent.NoTitleBar" />
            <action android:name="" />
            <category android:name="android.intent.category.DEFAULT" />

Step 2. Import the Vungle SDK

import com.vungle.warren.Vungle;
import com.vungle.warren.AdConfig;              // Custom ad configurations
import com.vungle.warren.InitCallback;          // Initialization callback
import com.vungle.warren.LoadAdCallback;        // Load ad callback
import com.vungle.warren.PlayAdCallback;        // Play ad callback
import com.vungle.warren.VungleNativeAd;        // MREC ad
import com.vungle.warren.Banners;               // Banner ad
import com.vungle.warren.VungleBanner;          // Banner ad
import com.vungle.warren.Vungle.Consent;        // GDPR consent
import com.vungle.warren.VungleSettings         // Minimum disk space
import com.vungle.warren.error.VungleException  // onError message

Step 3. Add Code

Initialize the SDK

In earlier versions of the Vungle SDK, we required you to pass a list of placement reference IDs, which we used in the session during initialization. Starting with Vungle SDK v6.3.12, we have removed this requirement. You can still use the legacy API, but we plan to deprecate in the future.

Now, with Vungle SDK v6.3.12 and higher, you can initialize the SDK without passing a Collection of placement reference IDs. All active placements for the application ID will be usable to play and load ad. 

// New v6 API
public static void init(@NonNull String appId,
                        @NonNull Context context,
                        @NonNull InitCallback callback)

// New since v6.4.11 API with optional minimum disk space configuration
public static void init(@NonNull final String appId,
                        @NonNull final Context context,
                        @NonNull final InitCallback callback,
                        @NonNull final VungleSettings settings)

// Legacy v6 API
public static void init(@NonNull final Collection placements,
                        @NonNull String appId,
                        @NonNull Context context,
                        @NonNull InitCallback callback)

The initialization method takes the following parameters:

  • Vungle Application ID
  • Application context
  • InitCallback
    • onSuccess: notifies when the SDK has successfully initialized
    • onError: notifies when the initialization has failed
      • Throws IllegalArgumentException if InitCallback is null.
      • Starting with Vungle SDK v6.5.1, throws VungleException if required arguments are missing or invalid. In Vungle SDK v6.4.11 and lower, Throwable object was passed.
    • onAutoCacheAdAvailable: notifies when the auto-cached placement has an ad available to play
  • VungleSettings (optional)
    • Specify minimum space available on device for SDK initialization and operation

For all placements, loadAd must be explicitly issued, as described in “Step 5. Load an Ad for a Placement.”

Vungle.init(appId, getApplicationContext(), new InitCallback() {
    public void onSuccess() {
        // Initialization has succeeded and SDK is ready to load an ad or play one if there
        // is one pre-cached already

    public void onError(VungleException exception) {
        // Initialization error occurred - exception.getLocalizedMessage() contains error message

    public void onAutoCacheAdAvailable(String placementId) {
        // Callback to notify when an ad becomes available for the cache optimized placement
        // NOTE: This callback works only for the cache optimized placement. Otherwise, please use
        // LoadAdCallback with loadAd API for loading placements.

You can check whether the Vungle SDK is initialized anytime by calling the isInitialized method:

public static boolean isInitialized()

Implement Event Listeners

If you plan to use generic callbacks for all events, implement LoadAdCallback for ad load events and PlayAdCallback for ad play events now. Otherwise, skip to “Step 5. Load an Ad” to implement inline callbacks.

Note: Starting with Vungle SDK v6.5.1, the onError callback for PlayAdCallback and LoadAdCallback passes VungleException, as opposed to a Throwable object passed in Vungle SDK v6.4.11 and lower.

// Implement LoadAdCallback
private final LoadAdCallback vungleLoadAdCallback = new LoadAdCallback() { 
  public void onAdLoad(String placementReferenceId) { 
    // Placement reference ID for the placement to load ad assets 

  public void onError(String placementReferenceId, VungleException exception) { 
    // Placement reference ID for the placement that failed to download ad assets 
    // VungleException contains error code and message 
// Implement PlayAdCallback
private final PlayAdCallback vunglePlayAdCallback = new PlayAdCallback() { 
  public void onAdStart(String placementReferenceId) { 
    // Placement reference ID for the placement to be played 

  public void onAdEnd(String placementReferenceId, boolean completed, boolean isCTAClicked) { 
    // Placement reference ID for the placement that has completed ad experience 
    // completed has value of true or false to notify whether video was 
    // watched for 80% or more 
    // isCTAClkcked has value of true or false to indicate whether download button 
    // of an ad has been clicked by the user 

  public void onError(String placementReferenceId, VungleException exception) { 
    // Placement reference ID for the placement that failed to play an ad 
    // VungleException contains error code and message

Load an Ad for a Placement

The LoadAdCallback will be notified about the load state for the call to which it was assigned. The SDK only references this callback and does not store it anywhere; it is the responsibility of the caller to ensure that the callback is managed properly.

public static void loadAd(@NonNull final String id, @Nullable LoadAdCallback callback)
// Load Ad Implementation
if (Vungle.isInitialized()) {
  Vungle.loadAd("PLACEMENT_ID", new LoadAdCallback() {
    public void onAdLoad(String placementReferenceId) { }

    public void onError(String placementReferenceId, VungleException exception) { }

Check Ad Availability for a Placement

Use the static method canPlayAdmethod to check if there is an ad available to play for the placement before invoking the playAd method.

public static boolean canPlayAd(@NonNull String id)

Play an Ad

To play an ad, invoke the playAd method with the placement reference ID, optional AdConfig (null if not being used), and a PlayAdCallback event listener, which will be notified of success or errors during ad playback.

public static void playAd(@NonNull final String id, final AdConfig settings, @Nullable final PlayAdCallback listener)

Always check ad availability by calling the canPlayAd method before invoking the playAd method. Because an ad will not render properly if playAd is repeatedly called in quick succession, you must also make sure that you receive either an onAdEnd or an onError callback from the initial playAd call before issuing an additional playAd.

if (Vungle.canPlayAd("PLACEMENT_ID")) { 
  Vungle.playAd("PLACEMENT_ID", null, new PlayAdCallback() { 
    @Override public void onAdStart(String placementReferenceId) { } 
    @Override public void onAdEnd(String placementReferenceId, boolean completed, boolean isCTAClicked) { } 
    @Override public void onError(String placementReferenceId, VungleException exception) { } 

Re-Initialize SDK When onError Occurs

On rare occurrences, resources can become limited, causing the system to deallocate either part of the Vungle SDK, or some of the third-party dependencies our SDK requires. In such cases, LoadAdCallback and PlayAdCallback fire an onError callback with a VungleException object, with the code VungleException.VUNGLE_NOT_INTIALIZED. This indicates that the Vungle SDK is in an inoperable state and must be re-initialized.

if (e.getExceptionCode() == VungleException.VUNGLE_NOT_INTIALIZED) {
  // Re-initialize Vungle SDK

Optional and Advanced Settings

Integrate MREC Ads

Starting with Vungle SDK version 6.4.11, Vungle supports MREC video ads, which do not require a fullscreen view. The container size to render an MREC ad is 300 x 250, which is the industry standard. MREC video ads can be set anywhere on the screen and the user can continue using the app while the ad is being played.

Load an MREC Ad

Loading an MREC ad is the same as loading a fullscreen ad. However, the placement must be configured to support an MREC feed. Please contact your Vungle account manager to enable MREC for a placement.

Display an MREC Ad

Because the view size is fixed, the container which is used to display the MREC ad must be specified to be 300dp x 250dp, and the view can be placed anywhere on the screen. This container is a RelativeLayOut.

You can place this RelativeLayout anywhere on the screen. You must then call AdConfig.setAdSize to specify the ad size to be AdConfig.AdSize.VUNGLE_MREC and pass this object when calling Vungle.getNativeAd to get the MREC ad object.

Finally, call the addView function to associate the container with the MREC ad. Vungle MREC plays with sound enabled as a default, but you can set the setMuted option to true to start the video muted.

private RelativeLayout mrecContainer = findViewById(...);

AdConfig adConfig = new AdConfig();

VungleNativeAd vungleNativeAd = Vungle.getNativeAd("MREC_ID", adConfig, vunglePlayAdCallback);
View nativeAdView = vungleNativeAd.renderNativeView();

Close an MREC Ad

Because you have added the MREC ad view to your container view, you must also remove it, in case the ad view disappears from the screen, the activity or fragment is destroyed, or the parent view container is recycled or destroyed. If you try to play another MREC ad without closing the previous ad, you may see unexpected behavior in your app. Therefore, invoke finishDisplayingAd to end the ad experience. We also recommend that you remove the view onAdEnd event.

private VungleNativeAd vungleNativeAd;

// Calling finishDisplayingAd when you want to finish displaying MREC Ad
// will trigger onAdEnd and will tell you when you can remove the child
// MREC view container 

// And removing empty ad view from container
public void onAdEnd(String id, boolean completed) {
    vungleNativeAd = null;

Attach and Detach the State of an MREC Ad

If the user scrolls to a point where the video ad is no longer visible on the screen, you must pause the video, and resume it when it is again visible. To control the pause and resume states, call setAdVisibility from the VungleNativeAd instance, and set it to true when the video is visible and to false when the video goes off screen. The setAdVisibility is not to be confused with View visibility: this setter informs Vungle SDK whether the MREC ad view is visible or not, and depending on it, the SDK pauses or resumes video playback.

  • Pause an MREC ad:
  • Resume an MREC ad:

Integrate Banner Ads

Vungle Banner is currently in BETA phase. Please contact your account manger directly for access to ensure a successful launch.

Vungle supports banner video ads starting with Vungle SDK v6.5.1. The container size to render banner ads can be 320x50, 300x50, or 728x90 (for tablets).

Banner ads can be set anywhere on the screen, and the user can continue using the app while the ad is being played.

Banner Size







728x90 (for tablets)

Load a Banner Ad

Loading a banner ad works differently than it does for other ad formats. There is a specific Banners API that you use to load, play, and check for ad availability. You must specify the size of the banner that you want to load, and the SDK will automatically refresh it with the time interval that you configured on the dashboard. You must also configure the placement to support a banner feed, so please contact your Vungle account manager to enable banner ads for a placement.

  • Load a banner ad by calling the loadBanner method:
    Banners.loadBanner("BANNER_ID", AdConfig.AdSize.BANNER, vungleLoadAdCallback);
  • Check for banner ad availability by calling the canPlayAd method:
    Banners.canPlayAd(ad.placementReferenceId, AdConfig.AdSize.BANNER);

Display a Banner Ad

Because the view size is fixed, you must specify the container used to display banner ads to be one of the supported sizes: 320x50, 300x50, or 728x90 (for tablets). You can place the view anywhere on the screen. This container is a LayOut. Its size must be equal to or greater than the banner size you are using. You can place this LayOut anywhere on the screen. Then you must pass the size of the banner you are using via the Banners API.

Pass this object when calling Banners.loadBanner to specify the size you are displaying, and use Banners.getBanner to get the Banners ad object. Finally, call the addView method to associate the container with the banner ad.

private RelativeLayout bannerContainer = findViewById(...);
// Check for banner ad availability and display
if (Banners.canPlayAd("BANNER_ID", AdConfig.AdSize.BANNER)) {
  VungleBanner vungleBanner = Banners.getBanner("BANNER_ID", AdConfig.AdSize.BANNER, vunglePlayAdCallback);

Close a Banner Ad

Because the banner ad view has been added to your container view, it must also be removed, in case the ad view disappears from the screen, the activity or fragment is destroyed, or the parent view container is recycled or destroyed. If you try to play another banner ad without closing the previous ad, you may experience unexpected behavior in your app.


Advanced Banner Configuration

For most cases, the integration described above is sufficient, and VungleBanner will be managed. However, if the VungleBanner view is inside a list or a RecyclerView, the managed VungleBanner will not work correctly. The moment the user scrolls the ad offscreen and scrolls back, the ad will be finished and no longer there. For such cases, we provide an advanced API for closer control of the VungleBanner. Refer to our main banner integration guide for more information.

Include Google Play Services

Including Google Play Services with your project is optional, but recommended. It enables Vungle to provide a more customized ad experience to your end user. We recommend that you include basement and ads-identifier APIs, and that you use version Google Play Services v11.0.1 or higher.

To include Google Play Services, refer to Google's setup guide. In your app, ensure that the device has a sufficiently updated version of Google Play Services. The Vungle SDK optionally uses the location and ads API from Google Play Services.

  • (Recommended)
  • (Required for AAID)

Method Count Reduction

Adding Vungle Android SDK v6 to your project adds approximately 700 core Vungle methods, excluding any transitive dependencies. A full integration including third-party libraries is expected to add less than 4000 methods on average. Consider the following suggestions to reduce the total number of methods added to your project:

  • ProGuard: You can enable ProGuard to shrink your project code. It will discard any unused classes at the time of compilation to make the total method count as small as possible. You can enable it by setting minifyEnabled to true in build.gradle for the appropriate build type, and by providing the rules to keep the classes required by your project.
  • MultiDex: If you are still above a 65K method count, enabling MultiDex may be the only solution provided by Google. You must only configure your project to MultiDex one time, but it will have an impact on build and app startup time.


If you are using ProGuard, add the following rules to your ProGuard configuration file:

# Vungle
-keep class com.vungle.warren.** { *; }
-keep class com.vungle.warren.downloader.DownloadRequest
-dontwarn com.vungle.warren.error.VungleError$ErrorCode
-dontwarn com.vungle.warren.downloader.DownloadRequest$Status
-keepclassmembers enum com.vungle.warren.** { *; }

# Moat SDK
-keep class com.moat.** { *; }
-dontwarn com.moat.**
-dontwarn org.codehaus.mojo.animal_sniffer.IgnoreJRERequirement
-keepattributes *Annotation*

# Retrofit
-keepattributes Signature, InnerClasses
-dontwarn org.codehaus.mojo.animal_sniffer.IgnoreJRERequirement
-dontwarn javax.annotation.**
-dontwarn kotlin.Unit
-dontwarn retrofit2.-KotlinExtensions
-keepclassmembers,allowshrinking,allowobfuscation interface * {
    @retrofit2.http.* <methods>;

# Okio+OkHttp
-dontwarn okhttp3.**
-dontwarn okio.**
-dontwarn javax.annotation.**
-dontwarn org.conscrypt.**
-keepnames class okhttp3.internal.publicsuffix.PublicSuffixDatabase
-keepclassmembers class * extends com.vungle.warren.persistence.Memorable {
   public <init>(byte[]);

Set Minimum Disk Space

Minimum disk space configuration was introduced in Vungle SDK v6.4.11 to determine the limits for available space on a user’s device before the Vungle SDK initializes and fetches ads. The default value for setMinimumSpaceForInit is 51 MB and setMinimumSpaceForAd is 50 MB. The size is entered in bytes.

VungleSettings vungleSettings = new VungleSettings.Builder()
    .setMinimumSpaceForInit(51L * 1024L * 1024L)  // 51 MB
    .setMinimumSpaceForAd(50L * 1024L * 1024L)    // 50 MB
Vungle.init(appId, getApplicationContext(), initCallback, vungleSettings);

Restrict Use of Device ID

Starting with Vungle Android SDK v6.4.11, you can now restrict the transmission of the Android ID used when the Google Advertising ID is not available.

// Set true to opt out for Android ID collection by SDK or false (default) to opt in
VungleSettings vungleSettings = new VungleSettings.Builder()
Vungle.init(appId, getApplicationContext(), initCallback, vungleSettings);

Ad Configuration Options

You have the option to customize individual ads you play by providing a new adConfig object to playAd. When the AdConfig object is null, the ad plays with the default configuration settings; when it is non-null, its settings override those in the AdConfig setter. The following is an example of how to use AdConfig:

Vungle.playAd(placementReferenceID, adConfig, vunglePlayAdCallback);

The above example uses the adConfig object, which contains customized configuration options. Set the AdConfig object as shown:

AdConfig adConfig = new AdConfig();
Vungle.playAd(placementReferenceID, adConfig, vunglePlayAdCallback);

The following table lists all the available AdConfig options:




'true' if the back button should be enabled before the close ad button appears; 'false' otherwise


AdConfig.AUTO_ROTATE if the video ad should auto-rotate; otherwise AdConfig.LANDSCAPE or AdConfig.PORTRAIT to follow video ad orientation


'false' if the video should start with its audio settings matching those of your enclosing application; 'true' if it should start muted regardless


takes an Integer value of ordinal count to track the number of ads that have been played in same session

Note: You may use the same AdConfig object for multiple ads.

Customize Rewarded Ads

The pop-up message dialog for rewarded ads is configurable with the setIncentivizedFields method.

Note: Rewarded ads are in some cases referred to as incentivized ads; both terms always refer to the same kind of ad. In the SDK code and in our Reporting API, we use the term 'incentivized'.
public static void setIncentivizedFields(@Nullable String userID, @Nullable String title, @Nullable String body, @Nullable String keepWatching, @Nullable String close)

List of Valid Placements

We provide a helper method that returns a Collection of Strings containing all valid Placement Reference IDs for the current session.

public static Collection getValidPlacements()

GDPR Recommended Implementation Instructions

As of May 25, 2019, the General Data Protection Regulation (GDPR) will be enforced in the European Union. To comply with GDPR, developers have two options.

  • Option 1 (recommended): Publisher controls the GDPR consent process at the user level, then communicates the user’s choice to Vungle. To do this, developers can collect the user’s consent using their own mechanism, and then use Vungle APIs to update or query the user’s consent status. Refer to the sample code below for details.
  • Option 2: Allow Vungle to handle the requirements. Vungle will display a consent dialog before playing an ad for a European user, and will remember the user’s consent or rejection for subsequent ads.

Thee updateConsentStatus method (recommended in Option 1) takes the user's consent status and the consent message version as its parameters.

ublic static void updateConsentStatus(@NonNull Consent status, @NonNull String consentMessageVersion)

The consent status will specify whether the user has OPTED_IN or OPTED_OUT for the message version you displayed. The consentMessageVersion specifies the publisher-controlled consent policy version; this enables you to pool your users by the message version and seek consent again when the GDPR policy changes.

// Usage example of GDPR API
// To set the user's consent status to opted in:
Vungle.updateConsentStatus(Vungle.Consent.OPTED_IN, “1.0.0”);

// To set the user's consent status to opted out:
Vungle.updateConsentStatus(Vungle.Consent.OPTED_OUT, “1.0.0”);

// To find out what the user's current consent status is:
// This will return null if the GDPR Consent status has not been set
// Otherwise, it will return Vungle.Consent.OPTED_IN or Vungle.Consent.OPTED_OUT
Vungle.Consent currentStatus = Vungle.getConsentStatus();
String consentMessageVersion = Vungle.getConsentMessageVersion();

Hardware Acceleration

Hardware acceleration is enabled by default for your application if your target API level is set to 14 or above. This option must be enabled for the SDK to properly show Dynamic Template and MREC ads. Make sure this option is set to 'true' at the application level of your project:

<application android:hardwareAccelerated="true" ...>

Retrieve the SDK Version Number

To programmatically retrieve the SDK version number at runtime (this useful in internal mediation), Vungle provides the following String:


Exception Codes for Debugging

InitCallback, PlayAdCallback, and LoadAdCallback will have a VungleException code when the onError callback fires. You can use the code to debug or take actions to correct the issue programmatically.

if (exception.getExceptionCode() == VungleException.VUNGLE_NOT_INTIALIZED) {
  // Call routine to initialize SDK
Exception Code Description
CONFIGURATION_ERROR A configuration error occurred. Check your app ID and placement reference IDs, and try again when network connectivity is available.
NO_SERVE Ad server found no advertisements for your current bid. Please try again later. This exception is expected behavior.
UNKNOWN_ERROR An unknown error occurred. This exception should be rare.
AD_EXPIRED The advertisement in the cache has expired and can no longer be played. Please load another ad.
MISSING_REQUIRED_ARGUMENTS_FOR_INIT Please ensure all parameters for Vungle.init() marked as NonNull are provided, as they are essential for the SDK to function.
APPLICATION_CONTEXT_REQUIRED Please provide the application Context so that our SDK can continue to support our API beyond the Activity lifecycle.
OPERATION_ONGOING There is already an ongoing operation for the action you requested. Please wait until the operation completes before starting another.
VUNGLE_NOT_INTIALIZED Vungle is not initialized, or no longer initialized. Please call Vungle.init() to reinitialize.
AD_UNABLE_TO_PLAY Unable to play advertisement.
AD_FAILED_TO_DOWNLOAD Advertisement failed to download.
PLACEMENT_NOT_FOUND Placement is not valid.
SERVER_RETRY_ERROR Remote server responded with HTTP Retry-After, the SDK will retry this request.

Configure Auto Backup for JAR Integration

The "allow backup" setting is enabled by default for your application for API 23 or higher. The backup rule ensures that all application data is backed up for proper operation of the Vungle SDK and of the app itself. If you have not disabled the "allow backup" setting or specified your own backup rules, you must provide additional XML rules to define which files in our SDK file system should be excluded from automatic backup.

Vungle Exclusion Rules

    <exclude domain="file" path="vungle" />
    <exclude domain="file" path="vungle_cache" />
    <exclude domain="external" path="vungle_cache" />
    <exclude domain="database" path="vungle_db" />
    <exclude domain="sharedpref" path="com.vungle.sdk.xml" />

Gradle Integration with Developer Backup Rules

  1. Add Vungle SDK exclusion rules to the existing .xml file that has your app’s own exclusion rules.
  2. Configure fullBackupContent to be replaced on the application level and add the Vungle SDK exclusion rule to the existing .xml.

JAR Integration with Developer Backup Rules

  1. Create a new XML file with Vungle exclusion rules.
  2. Place the .xml file under the res/xml directory.
  3. Add fullBackupContent in the application tag of AndroidManifest.xml with the file name of the .xml file you created above.

Disable Auto Backup

If backup is not required for your app, you can simply disable it on the application tag:

    android:allowBackup="false" >
Powered by Creativity Driven by Performance Sign Up Here


Need further assistance, feel free to reach out to us, we’re here to help!

Was this article helpful?