Currently, the latest Wortise version supported is 1.6.0 on our Ad Network Sdk, either on wortise-ads-sdk or multi-ads-sdk. The integration of Wortise ads in all our products is based on a cooperation agreement between us (Solodroid) and Wortise, then after consideration and for certain reasons, for the next update Wortise Sdk, we are currently holding it until an undetermined time limit, here are some reasons why we are doing this holding process:
There is no clarity from Wortise regarding the continuation of the Wortise SDK integration cooperation on our products.
Wortise is not cooperative and tends to be unresponsive so that the communication process does not run well.
Several parties or sources say that Wortise is a scam.
So from the points above, we decided to hold temporarily including the SDK update related to Wortise integration on our products. We also don't want to take any further risks, at the latest by the end of this year, if there is still no certainty, so with a heavy heart we will remove all Wortise SDK integration on all our products, and replace it with another Ad Network, we already have another alternative candidate (Pangle). If there are buyers who want to use Wortise, they will be included in the customization service and there will be an additional charge for that.
If you wish to continue using Wortise on our items, alternatively you can contact us directly for customization services. We guarantee that you will get the latest SDK update when it is available.
If you are interested, you can contact us via email: help.solodroid@gmail.com
The Cleartext traffic configuration is required for the app to run on http and https protocols, the cleartext traffic warning is not an error, but a warning which can be ignored.
But, if you want to solve or remove the warning, it's also can be removed, but with consequences and with note that the app will only run on https protocol, if you use http protocol, the content will not be able to be loaded from the server to the app.
To remove the warning, in the Android Studio project, open res/xml/network_config.xml, then, in the base-config cleartextTrafficPermitted configuration, change the value from trueto false, by using false value, the warnings message will be disappear when you publish the app on Google Play.
We offer a new option for Solodroid project users who want to monetize apps with certain ad networks as an alternative if AdMob experiences problems such as being restricted or even banned. In this case we use the single ads SDK format as a backup ad or even make it the main ad. By using a single ads SDK, the advertising SDK is used only on that ad network SDK so that the size of the aab/apk file when built is minimal or smaller and can minimize problems in publishing to the Google Play Store related to SDKs from other ad networks that may not or do not comply with policies.
Below are several single ads SDK implementation options that we have released and can be used.
Wortise Ads Sdk
1. Open build.gradle (Module: app) and change the implementation to wortise-ads-sdk
To solve this problem in our code, it is necessary to update the dependencies in the build.gradle (Module: app) file and in the MainActivity.java file. This applies in general to all codes from solodroid.
Step 1 (Updating dependencies)
Open the build.gradle (Module: app) file, find the library implementation below and remove it.
Add or change it with the 2 new libraries implementation below and Sync now. implementation 'com.google.android.play:review:2.0.1'
implementation 'com.google.android.play:app-update:2.1.0'
Step 2 (Updating MainActivity.java)
Open the MainActivity.java file, find the following code below, for quick search, use Ctrl + F. import com.google.android.play.core.tasks.Task;
Replace it with the code below, to make it faster, you can use Ctrl + R to replace the code with a new one: import com.google.android.gms.tasks.Task;
We provide several choices of ad network libraries that you can customize yourself based on monetization needs for your application.
The library implementation can be managed easily in the Android Studio project dependencies in the build.gradle (Module: app) file
1. AdMob ads sdk (recommended) 👍
admob-ads-sdk: using 1 main ads vendors from Google, overall it supports 2 ad networks: AdMob and Google Ad Manager. This library is suitable if you only want to monetize your app with ad providers from Google officially. The apk/aab file size will be smaller compared to using multi-ads-sdk because fewer ad libraries are used.
simple-ads-sdk: using 2 main ads vendors from Google and Facebook, overall it supports 3 ad networks: AdMob, Google Ad Manager and Meta Audience Network. This library is suitable if you only want to monetize your app with one or both of these ad providers from Google and Facebook. The apk/aab file size will be smaller compared to using multi-ads-sdk because fewer ad libraries are used.
triple-ads-sdk: using 3 main ads vendors from Google, Facebook and AppLovin, overall it supports 5 ad networks: AdMob, Google Ad Manager, Meta Audience Network, AppLovin Max and AppLovin Discovery. This library is suitable for those of you who want to use multiple ad networks from many vendors and to maximize the concept of switch ads and backup ads to switch between using other ad networks if one or several ad networks you use have problems. The apk/aab file size will be slightly larger around 2-4 Mb due to more ad libraries are used.
multi-ads-sdk: full integration with 9 ad networks. This library is suitable for those of you who want to use multiple ad networks from many vendors and to maximize the concept of switch ads and backup ads to switch between using other ad networks if one or several ad networks you use have problems. The apk/aab file size will be slightly larger around 3-5 Mb due to more ad libraries are used.
Important: using multiple-ads-sdk there are some risks, your application or Google Play account may be removed or even suspended because there are potential ad networks sdk other than Google and Facebook such as AppLovin, Unity ads, Start.io, ironSource and Wortise may be against Google Play policy.
5. No ads sdk
no-ads-sdk: Use this library if you don't want to monetize your app with any ad network at all.
Important : All ad network id units are placed in admin panel except AdMob App ID and AppLovin SDK Key, both ids must be integrated programmatically in android code inside res/value/ads.xml
Especially for Audience Network, Audience Network, If you choose to use Audience Network Bidding, please select Ad Network Type to be AdMob, Google Ad Manager, AppLovin Max or IronSource These Ad Networks support being a Mediation Partner although it's still a Beta version.
The problem with the Android Studio project failing to build is because currently our library cannot be accessed after an incident involving an attack on our GitHub account, which caused our account to be flagged and inaccessible to the public.
We apologize in advance because it is out of our control, to resolve this issue, we have created an alternative SDK migration so that the project can be rebuilt.
Do the steps below:
Open the build.gradle (Module: app) file
Change the dependencies name for Ad Network and Push Notification
Click Sync now to re-sync the project using the new library
Regarding the addition of the lauch duration of the app in the splash screen, the application has 2 methods:
Force display App Open Ads
Skip App Open Ads on Start App
If option number 1 is used, then the application works as follows:
Splash Screen > Load config.json > Load App Open Ads and Show > Start the Main Menu
In the load open ads process, this makes the duration of the splash screen longer because there is a process of loading ads from ad networks and waiting for a response from the ad to be displayed first before the user enters the application.
If option number 2 is used, the application works as follows:
Splash Screen > Load config.json > Start the Main Menu
In this option, the process of opening the application after splash is faster than number 1, because no open ads are displayed when the user starts the application, but open ads will still appear when the user opens the application from the background to the foreground or when user resume the app.
App Open Ads can be disabled from json remote config.
.png)
