Integrate Applovin via Mediation Network and test it on MediationTestSuite

[ManLok Wong]

I am testing the Applovin integation is it correct. I am using the MediationTestSuite to test it. I fixed the Adapter and Manifest error.

But I saw the Updater Initalization Status not reward, Application ID not found, SDK key not found, ZoneID not found.

How can I fix it?

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

 

Thank you for raising this to us.

 

Could you try following this guide (Integrating AppLovin with Mediation) and see if it works for you? If not, could you share to us your sample project (via Reply privately to author option) so we could further check on our end?

 

Regards,

Mark Albios

Mobile Ads SDK Team

ref:_00D1U1174p._5001USw2eY:ref

[ManLok Wong]

Thanks for reply. I know why application ID, sdk key zone id got error. Because I used the test app id. I created the new app id and new Applovin SDK key. Now these three thing was found.

But I still get adapter Initialization status not ready 

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

 

Thank you for getting back to me.

 

Could you further elaborate on those 3 things you've found? In addition, could you also share with me your App ID and Ad Unit Id/s privately ( via Reply privately to author option) for me to check on my end?

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

 

Thank you for sharing your Ad Unit Id in private.

 

I tried using your Ad Unit Id on our rewarded sample app and followed the steps below:

1. Import the AppLovin SDK and adapter
2. Added the Mediation Test Suite into the sample app.

 

After launching the Mediation Test Suite, I was successfully able to load and display the rewarded ad. Please see attached screenshots for your reference.

 

That said, could you try the steps mentioned above and let me know if it works on your end. If not, please share your sample project (via Reply privately to author option) so I could further check on my end.

[ManLok Wong]

I can load and play the ad using MediationTestSuite with Applovin. I was saw adapter Initialization Status not ready.

On Friday, January 10, 2020 at 9:27:07 AM UTC+8, ManLok Wong wrote:

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

 

Thank you for getting back to me. Would it be possible for you to share a sample project (via Reply privately to author option) where you encounter the issue (Adapter Initialization Status not ready) so I could further check on my end?

[ManLok Wong]

I am using the Unity project. Not a sample project.

On Friday, January 10, 2020 at 9:27:07 AM UTC+8, ManLok Wong wrote:

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

 

Since you're using a Unity project, I've followed the Unity guides below using our sample Unity project and I was able to properly setup the Mediation Test Suite on my end without any issues.

• Integrating AppLovin with Mediation
• Mediation Test Suite

 

That said, could you share the Unity project (or at least a sample project that is reproducing the issue) for me to take a closer look and further investigate? You may zip the entire Unity project (excluding the Library and Temp folders) in order to reduce its size, then send it to me via a shareable link from your Google Drive (or on any other file-sharing site that you prefer). Don't forget to send the shareable link via Reply privately to author option.

[ManLok Wong]

Hey, Can you see my private message?

On Friday, January 10, 2020 at 9:27:07 AM UTC+8, ManLok Wong wrote:

[Artoon Solutions]

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/axt5u000000000000000000000000000000000000000000000Q3VLK400OHVhoFspSayc4Go9yoGPCA%40sfdc.net.

[Mobile Ads SDK Forum Advisor Prod]

Hi ManLok,

 

If you were referring to your private message last February 11, 2020 that contained a copy of your sample Unity project, then yes, I was able to see the private message in question. Could you confirm if you received my reply to that message, sent on the same date? If not, then you may see below for a copy of my response back then:

 

Thank you for providing the requested project.

 

I was able to test the provided project, and can confirm the following conclusions:

• The mediation with the Facebook Audience Network (FAN) is working well (albeit getting a no-fill error when trying to load an ad), and
• The mediation with AppLovin has a manifest and an application ID error.

 

Kindly see attached screenshots. To solve the above issues with AppLovin, you may refer to two of the attached screenshots as well (applovin_manifest_fix and applovin_application_id_fix). Note that those screenshots were taken from this and this section of the AppLovin integration guide, respectively.

 

Let me know if you have any further questions.

 

However, if you already received the above, then I'm afraid I wasn't able to receive your latest private message after that one. Could you kindly resend it if this is the case?

 

Regards,

Ziv Yves Sanchez

Mobile Ads SDK Team

ref:_00D1U1174p._5001UV0gkp:ref

[ManLok Wong]

still not work. I still see the FAN and Applovin Adapter Initialization Status Not Ready. See below images.

On Friday, January 10, 2020 at 9:27:07 AM UTC+8, ManLok Wong wrote:

[Mobile Ads SDK Forum Advisor Prod]

Hi ManLok,

 

Kindly confirm if you're initializing the AdMob SDK first before initializing the Mediation Test Suite. You may also want to use the latest Facebook Audience Network (FAN) adapter (2.6.1) to ensure proper behavior.

 

As for the AppLovin application ID, have you confirmed that you were able to correctly input the above ID in your mediation setup in the AdMob UI (see attached screenshot)? If the situation persists despite the above, then I would recommend posting that particular concern over to the AdMob Help Center for further assistance, as the product specialists there should be able to provide more insights on such account-related concerns.

[ManLok Wong]

I have initialised the Admob SDK and downloaded and imported the FAN adapter 2.6.1 already. The 2.6.1 adapter only has the xml file.

On Friday, January 10, 2020 at 9:27:07 AM UTC+8, ManLok Wong wrote:

[Mobile Ads SDK Forum Advisor Prod]

Hi ManLok,

 

Thank you for confirming the suggestions previously provided.

 

Could you kindly provide the details below (via Reply privately to author) so that I can further investigate the issue?

• Copy of your sample project (replicating the issue)
• Steps to replicate the issue

[fahim hossin]

[Mobile Ads SDK Forum Advisor Prod]

Hi ManLok,

 

Thank you for providing the sample project in private.

 

I was able to build and test the project in question, and can confirm that the Adapter Initialization Status shows "Ready" on my end. I was also able to receive AppLovin ads despite the Manifest and Application ID sections showing as "Not found" (see attached screenshots). The Facebook adapter was giving me a no-fill error however, even though the Mediation Test Suite is reporting the successful initialization of all its parts.

 

Given the above, could you test the ads in that same project, and confirm whether or not you are getting any mediated ads from it? There shouldn't be any issue with regards to your setup if you were already getting ads in the app itself.

[ManLok Wong]

Hello. Do you change any setting on the project? I don't know why your Manifest not found in Applovin. I can find it.

Here is my log. The Applovin and FAN is Fail to create adapter

02-17 14:29:21.413  7486  7486 W Unity   : com.google.android.gms.ads.MobileAds:  Ready

02-17 14:29:21.413  7486  7486 W Unity   : UnityEngine.Logger:Log(LogType, Object)

02-17 14:29:21.413  7486  7486 W Unity   : Outblaze.BeastQuest.GoogleAdsMobController:<Awake>m__0(InitializationStatus)

02-17 14:29:21.413  7486  7486 W Unity   : System.Reflection.MonoMethod:Invoke(Object, BindingFlags, Binder, Object[], CultureInfo)

02-17 14:29:21.413  7486  7486 W Unity   : System.Reflection.MethodBase:Invoke(Object, Object[])

02-17 14:29:21.413  7486  7486 W Unity   : UnityEngine.AndroidJavaProxy:Invoke(String, Object[])

02-17 14:29:21.413  7486  7486 W Unity   : UnityEngine._AndroidJNIHelper:InvokeJavaProxyMethod(AndroidJavaProxy, IntPtr, IntPtr)

02-17 14:29:21.413  7486  7486 W Unity   :  

02-17 14:29:21.413  7486  7486 W Unity   : (Filename: ./Runtime/Export/Debug.bindings.h Line: 45)

02-17 14:29:21.413  7486  7486 W Unity   : 

02-17 14:29:21.418  7486  7486 W Unity   : com.google.ads.mediation.facebook.FacebookMediationAdapter: Failed to initialize adapter. com.google.ads.mediation.facebook.FacebookMediationAdapter does not implement the initialize() method. NotReady

02-17 14:29:21.418  7486  7486 W Unity   : UnityEngine.Logger:Log(LogType, Object)

02-17 14:29:21.418  7486  7486 W Unity   : Outblaze.BeastQuest.GoogleAdsMobController:<Awake>m__0(InitializationStatus)

02-17 14:29:21.418  7486  7486 W Unity   : System.Reflection.MonoMethod:Invoke(Object, BindingFlags, Binder, Object[], CultureInfo)

02-17 14:29:21.418  7486  7486 W Unity   : System.Reflection.MethodBase:Invoke(Object, Object[])

02-17 14:29:21.418  7486  7486 W Unity   : UnityEngine.AndroidJavaProxy:Invoke(String, Object[])

02-17 14:29:21.418  7486  7486 W Unity   : UnityEngine._AndroidJNIHelper:InvokeJavaProxyMethod(AndroidJavaProxy, IntPtr, IntPtr)

02-17 14:29:21.418  7486  7486 W Unity   :  

02-17 14:29:21.418  7486  7486 W Unity   : (Filename: ./Runtime/Export/Debug.bindings.h Line: 45)

02-17 14:29:21.418  7486  7486 W Unity   : 

02-17 14:29:21.424  7486  7486 W Unity   : com.google.ads.mediation.applovin.AppLovinMediationAdapter: Failed to create Adapter. NotReady

02-17 14:29:21.424  7486  7486 W Unity   : UnityEngine.Logger:Log(LogType, Object)

02-17 14:29:21.424  7486  7486 W Unity   : Outblaze.BeastQuest.GoogleAdsMobController:<Awake>m__0(InitializationStatus)

02-17 14:29:21.424  7486  7486 W Unity   : System.Reflection.MonoMethod:Invoke(Object, BindingFlags, Binder, Object[], CultureInfo)

02-17 14:29:21.424  7486  7486 W Unity   : System.Reflection.MethodBase:Invoke(Object, Object[])

02-17 14:29:21.424  7486  7486 W Unity   : UnityEngine.AndroidJavaProxy:Invoke(String, Object[])

02-17 14:29:21.424  7486  7486 W Unity   : UnityEngine._AndroidJNIHelper:InvokeJavaProxyMethod(AndroidJavaProxy, IntPtr, IntPtr)

02-17 14:29:21.424  7486  7486 W Unity   :  

02-17 14:29:21.424  7486  7486 W Unity   : (Filename: ./Runtime/Export/Debug.bindings.h Line: 45)

02-17 14:29:21.424  7486  7486 W Unity   : 

02-17 14:29:21.429  7486  7486 W Unity   : com.google.ads.mediation.unity.UnityMediationAdapter:  Ready

02-17 14:29:21.429  7486  7486 W Unity   : UnityEngine.Logger:Log(LogType, Object)

02-17 14:29:21.429  7486  7486 W Unity   : Outblaze.BeastQuest.GoogleAdsMobController:<Awake>m__0(InitializationStatus)

02-17 14:29:21.429  7486  7486 W Unity   : System.Reflection.MonoMethod:Invoke(Object, BindingFlags, Binder, Object[], CultureInfo)

02-17 14:29:21.429  7486  7486 W Unity   : System.Reflection.MethodBase:Invoke(Object, Object[])

02-17 14:29:21.429  7486  7486 W Unity   : UnityEngine.AndroidJavaProxy:Invoke(String, Object[])

02-17 14:29:21.429  7486  7486 W Unity   : UnityEngine._AndroidJNIHelper:InvokeJavaProxyMethod(AndroidJavaProxy, IntPtr, IntPtr)

Please see below screenshot.

On Friday, January 10, 2020 at 9:27:07 AM UTC+8, ManLok Wong wrote:

[Mobile Ads SDK Forum Advisor Prod]

Hi ManLok,

 

I did not change anything related to AndroidManifest.xml files within the project. If you are using ProGuard on your Unity project, could you try turning it off and seeing if it would fix the issue?

 

Apart from the above, you may try performing a full re-import of all the involved Unity plugins (AdMob, AppLovin, Facebook, Mediation Test Suite), and then running a Force Resolve using the Play Services Resolver. I will also be sending a copy of the project you sent me (both the folder and the built APK) to confirm its working status on your end, via a private email in order to protect sensitive data.

[ManLok Wong]

Hello. I downloaded your project and test the app. is work. But how to you build the apk?

I used gradle system to build the Android studio project.

On Friday, January 10, 2020 at 9:27:07 AM UTC+8, ManLok Wong wrote:

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

I work along with Ziv. I'll be assisting you in this.

You may directly build the APK on Unity UI by navigating to File > Build settings menu. From there, select Android from the list and click Switch Platform, then click the Click Build And Run button.

Regards,
Teejay Pimentel

[ManLok Wong]

Hello. I resolve my issue. Thanks for your Sample project. It let me knows which part is wrong. I don't put the FAN sdk and Applovin SDK on my project. Now all green. Thanks.

On Friday, January 10, 2020 at 9:27:07 AM UTC+8, ManLok Wong wrote: