Android
Note: Since version 15.4.6, Mintegral SDK has changed the SDK package name and the class file name of each advertisement type. Developers of the integrated SDK version before 15.4.6 need to modify the code usage of the new SDK after upgrading this version. The areas that need to be changed are:
1.Maven warehouse configuration address. Download dependent gradle statement.
2.SDK initialization code.
3.Call code for each advertisement type (the interface has not changed, the clas name has changed).
4.Obfuscation configuration information changes (if used), resource reduction configuration changes (if used), resource obfuscation whitelist configuration changes (if used), downloader adaptation changes (if used), see'AndoridManifest. xml configuration' column.
5.Developers who use jar package integration need to change the Activity registration information corresponding to the integrated advertising type.see'AndoridManifest. xml configuration' column.
</font>
Original class name
New class name
MIntegralSDKFactory
MBridgeSDKFactory
MTGBannerView
MBBannerView
MtgNativeHandler
MBNativeHandler
MTGMediaView
MBMediaView
MTGAdChoice
MBAdChoice
MTGNativeAdvancedHandler
MBNativeAdvancedHandler
MTGRewardVideoHandler
MBRewardVideoHandler
MTGInterstitialHandler
MBInterstitialHandler
MTGInterstitialVideoHandler
MBInterstitialVideoHandler
MTGInteractiveHandler
MBInteractiveHandler
MTGSplashHandler
MBSplashHandler
Overview
This document provides instructions on how to integrate the Mintegral SDK for Android developers. Mintegral SDK provides nine different Ads formats: Banner, Native, Native Video, Automatic Rending Native, Rewarded Video, Interstitial, Interstitial Video, Interactive and Splash.
Precautions for code use and navigation bar configuration information If the application you set in the background configuration page is to accept apk advertisements, you need to pass in the context object in the code when using any type of advertisement. Be sure to ensure that it is of the Activity type (the Application context object will have an abnormal effect). If the page (Activity) displaying the advertisement is full screen without navigation bar, please follow this link to add hidden navigation in your Activity The code of the bar, otherwise it may cause the navigation bar to display abnormally.
Import SDK
Please follow the tips below to choose your integration method, click "Start Integration" to get SDK.
Demo
When not integrating with gradle, in the zip package of the manual download SDK, there is a file named MBTest which is the Demo corresponding to this download version.
Get the current SDK version
MBConfiguration.SDK_VERSION
Note:If you fail to pull the code using gradle, add the maven warehouse configuration to the project root build.gradle file。
</font>
Screenshot show:
AndroidManifest.xml configuration
1.Required permission
If you imported the SDK for China-Mainland Traffic app , then you are required to get permission for "READ_PHONE_STATE".You need to apply for the permission in your java code if the android system is above 6.0.
2.Downloader adaptation(If you are using aar or gradle integration, you can ignore this step)。
(1)Update the Android.Support.v4 to 26.0.0 or above.
(2)Need to adapter the FileProvider when the targetSDKVersion >= 24. China-Mainland Traffic app required, Oversea Traffic app can be ignore. Add these codes in mb_provider_paths.xml
Add these codes in AndroidManifest.xml
3.Proguard
If you are using Proguard, add the following rules to your ProGuard configuration file:
(1)Support AndroidX
(2)Not support AndroidX
4.ShrinkResources
If you are using shrinkResources,add the following rules to your res/raw/keep.xml file:
5.AndResGuard
If you are using AndResGuard, add the following whitelist to your AndResGuard configuration file:
6.Smart download
Note: Turn on the smart download feature, that is, "Play video while downloading", will be beneficial to the success rate of the load of the advertisement.
For AndroidX, on the version 14.2.5 and later, if you want to enable this feature in Android9.0 and above, you need to configure.
For Android Support, on the version 10.5.0 and later, if you want to enable this feature in Android9.0 and above, you need to configure.
Configuration
(1) In the res directory, create a network_security_config.xml file with the following contents:
(2) Add the following configuration to the application tag of AndroidManifest.xml:
SDK Initialization
Add the Mintegral SDK to your project
As the first step of integration,you need to add the Mintegral SDK to your project.
Integrate via JAR/AAR package
File Name
File Function
same.jar/aar chinasame.jar/aar
Basic functions
mbbanner.aar.jar/aar
Banner ads package
mbnative.jar/aar
Native ads package
nativeex.jar/aar
Native Video ads package
mbnativeadvanced.jar/aar
Automatic Rending Native ads package
reward.jar/aar
Rewarded Video ads package
interstitial.jar/aar
Interstitial ads package
interactiveads.jar/aar
Interactive ads package
mbsplash.jar/aar
Splash ads package
playercommon.jar/aar
Video player basic package
videojs.jar/aar
Video player function package
videocommon.jar/aar
Video download basic package
mbjscommon.jar/aar
Java and H5 Interactive package
Tips: same.aar/chinasame.aar are basic function packages. that are required to be added into your project. If you want to implement other functions, you must add the corresponding ".aar" files. For example, to integrate Mintegral's Splash, you need to add same.aar/chinasame.aar, mbsplash.aar and its corresponding res folder into the project. If you use JAR package integration, in addition to adding the JAR package, you need to import its corresponding res file into the project.
Initialization
1.Put the initiating codes into Application through the respective App ID and App Key. See below example code for reference. It is recommended to use the API in the main thread, And Initialize The SDK as soon as your app starts.Ensure that the SDK is initialized only once in the application, you can refer to the MBridgeSDKManager.java tool class in Demo
We provide two ways to initialize the SDK:
(1)Initialization without callback
Sample code:
(2)Initialization with callback
Note:
For AndroidX, SDK provides callback for initialization status in version 14.1.0 and above.
For Android Support, SDK provides callback for initialization status in version 10.4.0 and above.
Sample code:
Preload Ads(Recommendation)
We provide the ability to preload for Native(NativeVideo) Ads formats. Preload is the process of loading the Ads ahead of time and saving it in cache.Here is the sample code:
Banner
Banner ads is the most traditional type of advertising for mobile advertising. It is easy to implement and highly user-acceptable. It is a good form of realization for ultra-casual games and tools.
UI sample:
Create the MBBannerView
Add MBBannerView to xml or dynamically add MBBannerView.
Note: SDK does not control the size of the View, so if you use dynamically loading MBBannerView, setLayoutParams is required to set the width and height of the view.
Example:
Introduction of BannerSize:
Introduction of MBBannerView APIs
Set up the BannerAdListener
Load And Show Ads
The request method is as follows:
Get advertising ID
For problems arising from the SDK display process, developers can use this API to record the advertising ID and feed it back to Mintegral The request method is as follows:
Release object of MBBannerView
Release the memory space of the MBBannerView object by calling the release() method at the appropriate time.
Sample code
Native(Native Video)
Native Ads is currently one of the most popular Ads types. The Mintegral SDK will report back creative material information to your app. You will then be able to assemble and adjust the creative elements as needed to ensure the creative material is compatible to your product style and in turn create the best user experience.
Note: This ad format is only available to certain developers, please contact your AM or write to developer@mintegral.com if needed.
UI sample:
Create the MBNativeHandler
It is recommended to use Application object for context param.
Set up the NativeAdListener
To set up Ads request tracking, the below set ups are required:
Set up the NativeTrackingListener
To set up Ads impression and click tracking, the below set ups are required.
Load Ads
When the Mintegral SDK calls this method, it will first read the Ads from the cache. If there is an AdAds in the cache, it will return directly, which will improve the display efficiency. If there is no cache, it will send an Ads request to the server to obtain the AdAds. Notes:It's not recommendation that publishers save the object of campaign by themselves The request method is as follows:
Display Ads
Use MBMediaView to display the Native(NativeVideo) Ads with "onAdLoaded" method. The best size of MBMediaView is 16:9.
Display Adchoice
We provide MBAdChoice to display the Adchoiceview. It is a class that inherits from ImageView. Call the following method to Display the Adchoice. Tip:We strongly suggest that developers can show this MBAdChoice(icon) in the right location in your app, if not, it will affect your ad revenue.
Set up your click-event for views
Release object of NaitveHandler
Release the memory space of the NativeHandler object by calling the release() method at the appropriate time.
Introduction of MBMediaView APIs
Sample code
Automatic Rending Native
The Automatic Rending Native launched by Mintegral is simpler than ordinary Native ads. Developers only need to provide a wide and high area, and Mintegral will automatically display the ad templates and materials that match it. While reducing developer docking costs, more efficiently use the Mintegral algorithm to output advertising ideas, thereby improving developer income levels.
UI sample:
Create the MBNativeHandler
Set up the NativeAdvancedAdListener
Some custom configurations
Native View Size
Recommend: 320 by 250
Mute
The mute button will only be displayed when a video is on the top of the layout (The specific proportion depends on the adaptation rules)
Close Button State
Auto Play Mode
H5 UI
You can customize the display layout of ads through JSON. Target can choose the following: title, subTitle, button, icon, container, mediaContent.
The JSON format is as follows:
Load Ads
Get advertising ID
For problems arising from the SDK display process, developers can use this API to record the advertising ID and feed it back to Mintegral The request method is as follows:
Check ads availability
Use the below method to determine whether a video material is ready to be played. It is strongly recommended to display ads only when the video material is ready to be played.
Display Ads
Get Ad View
Add the view to the specified container
Notify SDK
Release object of MBNativeAdvancedHandler
Release the memory space of the MBNativeAdvancedHandler object by calling the release() method at the appropriate time.
Sample code
Rewarded Video
Rewarded Video is one of the best performing Ads formats on the Mintegral platform. Users can get rewards by watching a video Ads. The creativity and attention-grabbing nature of the video content attracts users to download the advertised product.
Rewarded Video sample:
HardwareAccelerated
Add these codes "android:hardwareAccelerated=true" in tab of application:
Create the MBRewardVideoHandler
Set up the RewardVideoListener
Note: For void onAdClose (boolean isCompleteView, String rewardName, float rewardAmout), the two parameters rewardName and rewardAmout in this method are meaningless, and we will not send rewards. Therefore, you can decide whether to send rewards to users according to isCompleteView.
Set Mute
Please call playVideoMute before call load method.
Reward Plus Setting
Must be called before load This API only means accepting the advertisement of Reward plus, and issuing rewards still depends on the amount of reward currency information parameters (RewardName, RewardAmout) in the onAdClose() callback in the SDK for reward distribution.
Load and display Ads
It is recommended that developers preload Ads before displaying them (either during initialization or after closing each ad). This way, it allows more time for the creative material to download and also decreases the amount of wait time for users to see an ad. Use the below method to load and display ads.
Get advertising ID
For problems arising from the SDK display process, developers can use this API to record the advertising ID and feed it back to Mintegral The request method is as follows:
Check ads availability
Use the below method to determine whether a video material is ready to be played. It is strongly recommended to display ads only when the video material is ready to be played.
Sample code
Set up "Server to Server" to return the Ad reward
Based on your needs, you can choose to set up callback through SDK or through server to server. If you set up callback through server to server, Mintegral will use the callback URL to return reward information after a video ad is played.
1.Set up the callbackURL in the dashboard
When the user watches the video completely, Mintegral's server will request the callback URL to send the reward infomation to your server.
2.For the callback URL, developers only need to change the domain name. Example: https://www.sampleurl.com/mintegral?user_id={user_id}&trans_id={trans_id}&reward_amount={reward_amount}&reward_name={reward_name}&sign={sign}&unit_id={unit_id}&extra={extra}
3.When the Mintegral server recognizes that a user_id has earned a reward, it will inform the developer's server through the callback URL. Additional parameters of the callback URL are as follow:
Parameter
Description
user_id
User ID,set by developer
reward_amount
Amount of reward users should receive
reward_name
Reward name
unit_id
Unit ID
trans_id
Transmission ID, generated by Mintegral server, therefore is a unique ID
sign
Encryption identifier MD5(user_id_reward_amount_trans_id_security_key)
4.Once the developer's server receives the postback, it will need to return 200 or 403 to the Mintegral server.
5.If no response is received from the developer's server 20 seconds after the Mintegral server initiates a postback, Mintegral will retry every 5 minutes for the next 24 hours.
Static Interstitial
The interstitial ad will display a large image ad on the screen, and the user can close the ad by clicking the close button.
Note: This ad format is only available to certain developers, please contact your AM or write to developer@mintegral.com if needed. In addition, Mintegral has launched a new Interstitial Video ad type that offers better visuals and experience than regular Interstitial ads.
Interstitial sample:
Create the MBInterstitialHandler
Set up InterstitialListener
Load and display Ad
Get advertising ID
For problems arising from the SDK display process, developers can use this API to record the advertising ID and feed it back to Mintegral The request method is as follows:
Sample code
Interstitial Video
Interstitial Video ads are upgraded versions of Static ads that show users a full-screen or half-screen video, increasing user interest through more engaging videos.
Interstitial Video sample:
Create the MBInterstitialHandler
Set up InterstitialVideoListener
Set Mute
Please call playVideoMute before call load method.
Set the reward alert dialog mode for interstitial video.
Please call setIVRewardEnable before call load method.
Sample code
Custom the reward alert dialog display text.
You‘d better call setAlertDialogText before call load method.
Sample code
Load and display Ad
Get advertising ID
For problems arising from the SDK display process, developers can use this API to record the advertising ID and feed it back to Mintegral The request method is as follows:
Check ads availability
Use the below method to determine whether a video material is ready to be played. It is strongly recommended to display ads only when the video material is ready to be played.
Sample code
Interactive Ads
Interactive ad is a new ad format launched by Mintegral, in which users can instantly experience any app or game in the highest quality possible, before the download.This greatly improves the possibility of conversion. The current ads creatives are mainly interactive videos and HTML5 files.
Note: This ad format is only available to certain developers, please contact your AM or write to developer@mintegral.com if needed.
Sample UI:
Create the MBInteractiveHandler
Set up InteractiveAdsListener
Load and display Ad
It is recommended that developers preload Ads before displaying them (either during initialization or after closing each ad). This way, it allows more time for the creative material to download and also decreases the amount of wait time for users to see an ad. Use the below method to load and display ads.
Get advertising ID
For problems arising from the SDK display process, developers can use this API to record the advertising ID and feed it back to Mintegral The request method is as follows:
Sample code
Splash Ads
SplashAD is one of the most popular forms of advertising. This type is more suitable for placing e-commerce and brand advertisements, and traffic access is also very suitable for accessing application-type traffic. Users can click on the ad to jump to the ad landing page, or click on the "skip" button in the upper right corner to jump to the app content home page. It will load when your app is opened, and automatically close and enter your app's main interface after the display is complete.
Style: There are two styles of half-screen and full-screen ads. In the case of half-screen, it supports the definition of logo images, and also supports vertical and horizontal screens.
Splash Ad UI sample:
Androidmanifest.xml configuration
Add the following configuration to the corresponding activity:
The screenOrientation can be customized.
Create the MBSplashHandler
Set timeout(optional)
loadTimeOutMs: If the SDK does not complete the ad loading (i.e. the load times out) within a specified time, it closes directly. The unit is s.
Other sets
Set the logo size、direction。 Note: 1. LogoView's size should not greater than 25% of the device's size 2. The default orientation is vertical
Set up MBSplashLoadListener
Note:If the reqType is equal to 1,it means the callback of the preLoad; and if 2, it means the callback of the loadAndShow.
Set up MBSplashShowListener
Load and show ads
There are two ways to load and show ads:
Load ads first, and then show at the right time, which two steps are separated.
Load and show ads, which two steps are done by one method.
Get advertising ID
For problems arising from the SDK display process, developers can use this API to record the advertising ID and feed it back to MBridge The request method is as follows:
IsReady
Whether or not if there was a available ad to show.
Note: Please call preload at an appropriate time. The interval between preload and show should not be too long during the life cycle of the app. It is recommended that it should not exceed 30 minutes. After calling preload, when you need to show, you can use isready to determine whether it can be displayed. If it is ready, call show. If it is not ready, you can call load & show.
Notify SDK
Sample code
Test ID
The ads you get during the test are official Mintegral ads, so they will be affected by the intelligent optimization of the algorithm. If load fails frequently during the test and returns EXCEPTION_RETURN_EMPTY, you can use the following test id for testing.
AppKey
7c22942b749fe6a6e361b675e96b3ee9
AppID
118690
Ad format
Placement ID
Sample ad unit ID
Banner
138791
146879
Native
138780
146868
Feeds Video
138788
146876
Offerwall
138789
146877
Rewarded Video
138786
146874
Static Interstitial
138783
146871
Interstitial Video
138781
146869
Interactive Ads
138790
146878
Splash
173349
209547
Automatic Rending Native
202132
258656
Best Practices and FAQs
Integration recommendations
1.Initialize the SDK in Application. 2.After a successful load in onAdLoaded, preload the ads to improve the ad display speed in your app and in turn your overall UX and revenue. 3.You must match the ViewGroup when registering, do not only match the button. Confirming which area of your ad is clickable will be directly related to your revenue. 4.You can use TextView to display the CTA buttons; do not use Button as it will intercept events. 5.Each ad unit corresponds to a MBNativeHandler, so it is important to ensure the uniqueness of each ad unit. 6.Preload the App Wall when user reaches the homepage of the app. 7.For any Rewarded Video ads achieved through the Android SDK version 8.4.0, it is not recommended to use isReady() to determine whether the video is ready to be played when in onVideoLoadSuccess().
FAQs
1.Why are some the ads in Chinese even though the phone's language is set to English? A: The ad content is related to the user's network IP and not the phone's language setup.
2.Why do the ads jump so slowly for the first time? A: The ads will go through several layers of 302 redirects before reaching the final URL. The NativeHandler is notified when the page jump is complete and developers can setup a loading dialogue at this time.
3.Why does it black screen when a Rewarded Video is jumping back from the Google Play store? A: Make sure that the Rewarded Video is declared in the manifest.xml file like the below as follows:
The description of return-status
message
description
EXCEPTION_RETURN_EMPTY
ads no fill.Possible reasons: 1. The ads you get during the test are official ads of Mintegral, so they will be affected by the intelligent optimization of the algorithm. If the ads are loaded and displayed in a large amount of time, it may lead to no ads filling after a period of time. 2. The app is on Google Play, but the network status of the test is the China mainland network. 3.Not add package name in dashboard. 4. The blacklist is the category of ads that you don't want to show. Please don't select all in your dashboard.
EXCEPTION_SIGN_ERROR
AppID and appKey do not match correctly
EXCEPTION_TIMEOUT
request timeout
EXCEPTION_UNIT_NOT_FOUND
Can not find the unitID in dashboard
EXCEPTION_UNIT_ID_EMPTY
unitID is empty
EXCEPTION_UNIT_NOT_FOUND_IN_APP
Can not find the unitID of the appID
EXCEPTION_UNIT_ADTYPE_ERROR
The adtype of the unitID is wrong
EXCEPTION_APP_ID_EMPTY
appID is empty
EXCEPTION_APP_NOT_FOUND
Can not find the appId
EXCEPTION_IV_RECALLNET_INVALIDATE
The network status at the time of the request is incorrect. Generally, because of the SDK initialization is not completed yet when the request has been sent .
EXCEPTION_SERVICE_REQUEST_OS_VERSION_REQUIRED
Can not find the os_version,generally caused by GDPR switch.
NO_ADS_SOURCE
No ad source
data load failed, errorMsg is No video campaign
No video campaign Possible reasons: 1. The app corresponding to the current ad has been installed. 2. Please check if there is a video URL in the returned json data.
data load failed, errorMsg is load no ad
Load no ad
data save failed
The zip data of H5 save failed
data load failed, errorMsg is Network error,please check
Network error Possible reasons: 1. After the API is requested, the network status is unavailable. 2. After the API is requested, the API's resp of http is empty.
content write failed
Source code of H5 write failed
file is not effective
The video file is not effective Possible reasons: 1. Check whether the video file exists. 2. The video file is a file, not a folder. 3. The video file is readable.
MD5 check failed
MD5 check failed,which may caused by the MD5 content of the video file does not match that issued by the server or the MD5 exception generated by Client .
data load failed, errorMsg is The server returns an exception
The server returns an exception. There are two possible reasons. The first one is that code returned by the server is neither 200 nor 206,the second one is that the body is empty when the code is OK.
resource load timeout
Resource load timeout
CURRENT_UNIT_IS_LOADING
Current unit is loading,possibly because of loading again before the end of current load.
EXCEPTION_FILTER_BY_PLACEMENTID_INCONSISTENT
PlacementId is incorrect
EXCEPTION_UNIT_BIDDING_TYPE_ERROR
Bidding type is error,recreate a new unitID for bid
Notice for the EU-GDPR Modified SDK
On May 25th, 2018, the European Union’s General Data Protection Regulation (GDPR) went into effect. Developers need to update all Mintegral SDKs and integrate following the below description in the future. If not integrated with the below steps in mind, your ad serving will be affected.For now,The SDK which is above 8.11.0 can support GDPR. At the same time, we have updated the Bridgee Privacy Policy. for your reference.
API introductions
1.To set up the on and off switch to allow SDK to retrieve users' infomationyou will need to adopt the below code before SDK initialization.
Sample code
Tips
1.If you do not enable the SDK to gather users' information, it will affect overall ad serving and possibly result in no ad returns.
2.When integrating the SDK for apps used by EU users, it is recommended that developers obtain users' consent before initializing the SDK.
CCPA Preparation
On June 28, 2018, the State of California ("California") issued the California Consumer Privacy Act 2018 ("CCPA"), which aims to strengthen consumer privacy and data security protection, which will be effective On January 1st, 2020. For California users, you can use the setDoNotTrackStatus API to limit data processing based on the user's selection. After the setup is completed, Mintegral will no longer show personalized recommended ads to the user based on the their device information, and will not sync the device information to other third-party partners. The API is available in SDK version 12.1.2 and above.
API introductions
Whether to obtain user information should to be setted. And When calling this method, make sure that the SDK initialization has been called.
Sample code
Change log
Version
Change Log
Date
15.5.4
1. Increase SDK stack information reporting in the ad load stage 2. Several bug fixes
June 9, 2021
15.5.3
1. apk download compliance 2. The pop-up page supports dynamic native
June 4, 2021
15.5.2
1. Own id upgrade 2. Fix known issues
May 11, 2021
15.5.1
1. Video player updated to ExoPlayer 2. Synchronous download and playback of videos no longer rely on developer configuration 3. Domestic version downloader optimization 4. Performance optimization
April 27, 2021
15.5.0
1. Optimize apk download 2. Restore and optimize setting campaign reporting 3. Remove the logical judgment of deeplink in the load phase 4. Performance optimization
April 13, 2021
15.4.6
1. Change SDK package name 2. Several code optimizations
February 23, 2021
15.4.5
1. Improve SDK stability 2. Fix some bugs
February 18, 2021
15.3.1
1. Fix the problem that video playback fails in some cases 2. Fix the problem that ExcludeIds in RV/IV advertising styles are not reported
November 24, 2020
15.3.0
1. V3 interface upgrade and optimization 2. Adapt to Android special-shaped screen 3. Fix the problem that the new download module may fail due to confusion
November 20, 2020
15.2.4
1. Delete the string related to JS 2. Delete the API related to battery 3. Improve sdk stability
November 11, 2020
15.2.2
1. Optimize the SDK Demo 2. Change SDK user data parameters 3. Delete some non-core parameters under the build class
November 5, 2020
15.2.1
1. Fix some problems 2. Improve sdk stability
November 3, 2020
14.6.2
1. Supports AndroidX 2. Improve sdk stability
October 30, 2020
14.6.1
1. Supports AndroidX 2. Optimize deeplink 3. Improve sdk stability
October 23, 2020
14.6.0
1. Supports AndroidX 2. oaid acquisition method is fully upgraded 3. Internal webview supports deeplink jump
October 17, 2020
14.5.0
1. Supports AndroidX 2. Add the acquisition of advertising ID 3. Added download confirmation logic for secondary pop-up window 4. Fixed some bugs
September 18, 2020
14.4.6
1. Supports AndroidX 2. Improve sdk stability
September 17, 2020
14.4.5
1. Supports AndroidX 2. Fixed some bugs
September 14, 2020
14.4.4
1. Supports AndroidX 2. Fixed some bugs
September 04, 2020
14.4.0
1. Supports AndroidX 2. Add Reward Plus 3. Optimized SDK 4. Fixed some bugs
August 13, 2020
14.3.0
1. Supports AndroidX 2. Added callback of when the video played completely and videoLength property for NativeVideo ad format 3. Optimized SDK 4. Fixed some bugs
July 24, 2020
14.2.6
1. Supports AndroidX 2. Optimized SDK 3. Fixed some bugs
July 21, 2020
14.2.5
1. Supports AndroidX 2. Remove networkSecurityConfig 3. Fixed some bugs
July 09, 2020
14.2.3
1. Supports AndroidX 2. Fixed some bugs
July 04, 2020
14.2.2
1. Supports AndroidX 2. Optimized SDK 3. Fixed some bugs
Jun 30, 2020
14.2.1
1. Supports AndroidX 2. Optimized SDK 3. Fixed some bugs
Jun 30, 2020
14.2.0
1. Supports AndroidX 2. Fixed some bugs
Jun 23, 2020
14.1.0
1. Supports AndroidX 2. Added callback for SDK initialization success and failure
Jun 8, 2020
14.0.0
1. Supports AndroidX 2. Added Automatic Rending Native 3. Fixed some bugs
May 26, 2020
13.1.1
1. Supports AndroidX 2. Fixed some bugs 3. Optimized SDK
Apr 27, 2020
13.1.0
1. Supports AndroidX 2. Add placementId when all ad formats are initialized 3. Fixed some bugs
Apr 16, 2020
13.0.4
1. Supports AndroidX 2. Optimized the load process: reduce the occurrence of timeout and optimized the problem of callback to developers when multiple loads are triggered 3. Fixed some bugs
Mar 26, 2020
13.0.3
1. Supports AndroidX 2. Fixed the reporting problem of splash's impression
Mar 20, 2020
13.0.2
1. Supports AndroidX 2. Fixed the load timeout problem caused by check isready under weak network conditions 3. Removed high-risk code from runtime
Mar 20, 2020
13.0.1
1. Supports AndroidX 2. Fixed some bugs
Mar 12, 2020
13.0.0
1. Supports AndroidX 2. Added Splash 3. Adapt to download progress bar in Chinese and English 4. Fixed some bugs
Mar 09, 2020
12.2.3
1. Supports AndroidX 2. Fixed some bugs
Mar 05, 2020
12.2.2
1. Supports AndroidX 2. Optimized SDK
Mar 03, 2020
12.2.1
1. Supports AndroidX 2. Fixed an issue that could prevent NativeVideo from playing properly
Feb 20,2020
12.2.0
1. Supports AndroidX 2. Added the setting of the reward dialog when the video or playable is playing, or the user clicks close button for IV 3. Optimized mute setting which subjects to developer 4. Optimized SDK
Feb 16,2020
12.1.5
1. Supports AndroidX 2. Added the callback for closing the banner
Jan 10, 2020
12.1.2
1. Supports AndroidX 2. Supports smart download 3. Fixs the error that the aa class cannot be found
Dec 26, 2019
12.1.1
1. Supports AndroidX 2. Fixs the impression issues of BannerView
Dec 19, 2019
12.1.0
1. Supports AndroidX 2. Fixs the exception of bitmap 3. Optimized SDK
Dec 13, 2019
12.0.0
1. Supports AndroidX 2. Fixs the exception of NV impression callback
Dec 06, 2019
10.9.0
1. Not support AndroidX 2. Improve sdk stability
November 19, 2020
10.8.0
1. Not support AndroidX 2. Improve sdk stability
October 19, 2020
10.7.1
1. Not support AndroidX 2. Fix compatibility issues with 4.4 and below
September 24, 2020
10.7.0
1. Not support AndroidX 2. Add the acquisition of advertising ID 3. Added download confirmation logic for secondary pop-up window 4. Fixed some bugs
September 18, 2020
10.6.6
1. Not support AndroidX 2. Improve sdk stability
September 17, 2020
10.6.5
1. Not support AndroidX 2. Fixed some bugs
September 15, 2020
10.6.4
1. Not support AndroidX 2. Fixed some bugs
September 04, 2020
10.6.0
1. Not support AndroidX 2. Add Reward Plus 3. Fixed some bugs
August 17, 2020
10.5.1
1. Not support AndroidX 2. Added callback of when the video played completely and videoLength property for NativeVideo ad format 3. Optimized SDK 4. Fixed some bugs
July 27, 2020
10.5.0
1. Not support AndroidX 2. Remove networkSecurityConfig 3. Fixed some bugs
July 10, 2020
10.4.0
1. Not support AndroidX 2. Added callback for SDK initialization success and failure 3. Optimized SDK 3. Fixed some bugs
July 01, 2020
10.3.0
1. Not support AndroidX 2. Added Automatic Rending Native and Splash 3. Fixed some bugs
May 27, 2020
10.2.5
1. Not support AndroidX 2. Fixed some bugs
May 14, 2020
10.2.4
1. Not support AndroidX 2. Fixed some bugs
Mar 12, 2020
10.2.3
1. Not support AndroidX 2. Optimized SDK
Mar 03, 2020
10.2.2
1. Not support AndroidX 2. Fixs the issue that the offer may expire due to incorrect judgment when “Setting” cannot be obtained 3. Fixs the issue where white bars might appear at the top of specific scenes in NativeVideo
Feb 26,2020
10.2.1
1. Not support AndroidX 2. Added the callback for closing the banner
Jan 10, 2020
10.2.0
1. Not support AndroidX 2. Supports smart download 3. Fixs the error that the aa class cannot be found
Dec 30, 2019
10.1.9
1. Not support AndroidX 2. Fixs the impression issues of BannerView
Dec 18, 2019
10.1.8
1. Not support AndroidX 2. Fixs the exception of NV impression callback
Dec 06, 2019
10.1.7
1. Not support AndroidX 2. Fixs the crash of MBActivity and callback of Banner
Nov 29, 2019
10.1.6
Customized for AndroidX
Nov 14, 2019
10.1.0
1. Support om 2. Support Mraid expand 3. Banner callback optimization
sep 24,2019
10.0.0
Add Banner
Aug 27,2019
9.13.1
1. Support Mraid
Jul 09, 2019
9.12.4
1. Add Heading-Bidding
Jun 20, 2019
9.12.2
Remove Geolocation related code
Jun 14, 2019
9.11.0
Optimized SDK
May 10, 2019
9.10.0
Optimized RV and IV
Mar 25, 2019
9.9.1
Optimized Nativevideo
Mar 12, 2019
9.9.0
Optimized SDK
Mar 06, 2019
9.8.0
Optimized SDK
Feb 22, 2019
9.7.0
Fixs some bugs
Feb 01, 2019
9.6.0
Add Adchoice
Jan 10, 2019
9.5.0
Optimized the adapters for downloading
Dec 28, 2018
9.3.0
Supports to deeplink jump
Dec 06, 2018
9.2.0
Optimized the adapters for downloading
Oct 28, 2018
9.1.1
Supports to wechat mini program, Supports to https
Oct 28, 2018
9.0.0
Added interactive ad
Sep 25, 2018
8.13.0
Supports to obtain imei,mac,android id
2018.06.27
8.12.0
Added shortcuts
2018.06.13
8.11.0
Supports GDPR
May 20, 2018
8.10.0
Added Interstitial Video
May 10, 2018
8.9.0
The endcard can be auto-closed
Mar 26, 2018
8.8.0
Mediaview supports gif
Mar 12, 2018
8.7.0
Optimized all ad formats
Feb 29, 2018
8.6.0
Supports mute when video is playing
Jan 26, 2018
8.5.0
Video can be played in a loop
Dec 04, 2017
8.4.0
Fixed a portion of cell phone compatibility issues
Nov 14, 2017
8.3.0
Allows RV to be closed ahead of time and some other optimizations
Sep 04, 2017
8.2.0
Added Native Video
Aug 02, 2017
8.1.0
Added Offer Wall and Interstitial
Feb 14, 2017
8.0.0
Optimized Native and App Wall memory leaks
Dec 06, 2016
Last updated
Was this helpful?