Previously, we were using Unity 2021.3.29f1 to make our builds with EDM4U 1.2.176. We use AppLovin MAX Unity SDK for ad mediation. When resolving dependencies with EDM4U, it would put the .aar files into the Assets/Plugins/Android folder.
Since Google has the API 34 requirement, we updated to Unity 2021.3.42f1 and EDM4U 1.2.182. When I tried to resolve our dependencies, I got a popup saying the current preferred method is to let Gradle handle adding the dependencies to the build using various Gradle templates. So I updated the settings to let it do just that.
But when I build an APK now, it seems Gradle doesn’t to add all (or possibly any) of the dependencies to the APK. This causes the AppLovin post Gradle script to throw an error saying the Quality Service Plugin failed to be added to the build and it causes apkanalyzer to spit out an error saying it can’t estimate the build size due to a java.lang.ClassNotFoundException error. And when I load the APK on my test device with logcat running, it hangs because it cannot find the Android classes needed to connect to Google Play Games.
Since Google requires target API 34, downgrading Unity seems out of the question. And unfortunately, reverting to EDM4U 1.2.176 doesn’t seem to fix the issue at all.
I’m not well versed in Gradle, so I’m not sure what my options are to fix this issue. Any help would be much appreciated.
I guess first thing to see what dependencies are added, locate gradle project somewhere in Library/Bee/Android folder and take a look at unityLibrary/build.gradle file.
I can’t progress beyond that, so I don’t know what other libraries might be missing yet unless I remove the login requirement.
No, I did not add that. And it’s not in any of my Gradle template files, either. I’m guessing that’s the reason why our Google Play login breaks. Perhaps there’s a setting I activated in EDM4U that causes that section to get added?
I wrote a IPostGenerateGradleAndroidProject script to brute force remove the configurations.implementation section just to see if that would help any and it did. I now get a build that does include com.android.support and com.google.android.gms and allows me to load into the game.
I still get the two build error messages stating:
Error [AppLovin MAX] Failed to add AppLovin Quality Service plugin. Quality Service Plugin Added?: False, Quality Service Repo added?: False, Quality Service dependency added?: False
and
System.Exception: apkanalyzer failed to estimate the apk size. Output:
Error: Could not find or load main class Files\Unity\Hub\Editor\2021.3.42f1\Editor\Data\PlaybackEngines\AndroidPlayer\SDK\cmdline-tools\6.0\bin\\..
Caused by: java.lang.ClassNotFoundException: Files\Unity\Hub\Editor\2021/3/42f1\Editor\Data\PlaybackEngines\AndroidPlayer\SDK\cmdline-tools\6/0\bin\\//
The AppLovin SDK does initialize, but it can’t seem to load any of the ad libraries, so I suspect those are still missing from the APK.
My last response disappeared somehow…sorry if this winds up a double post.
I wrote a IPostGenerateGradleAndroidProject script that removed the configurations.implementation section from the build.gradle file to see if that helped any. It seems to have allowed the classes from com.android.support and com.google.android.gms to be added to the APK. I was able to at least load into our game after it attempted to log in to Google Play Store.
The build does still show these two error messages after an APK is generated in Unity:
#1
Error [AppLovin MAX] Failed to add AppLovin Quality Service plugin. Quality Service Plugin Added?: False, Quality Service Repo added?: False, Quality Service dependency added?: False
#2
System.Exception: apkanalyzer failed to estimate the apk size. Output:
Error: Could not find or load main class Files\Unity\Hub\Editor\2021.3.42f1\Editor\Data\PlaybackEngines\AndroidPlayer\SDK\cmdline-tools\6.0\bin\\..
Caused by: java.lang.ClassNotFoundException: Files\Unity\Hub\Editor\2021/3/42f1\Editor\Data\PlaybackEngines\AndroidPlayer\SDK\cmdline-tools\6/0\bin\\//
When loading the game up, the AppLovin SDK does initialize, but none of the ad libraries we use are loading. Logcat has a huge section of error messages like this:
k <init> cannot load Chartboost
k <init> cannot load AppLovin
k <init> cannot load AdMob
k <init> cannot load Fyber
I suspect that means those dependencies are missing from the APK.
AppLovin issued an update over the weekend. That fixed the AppLovin Quality Service plugin error.
But the apkanalyzer error still remains and the generated APK is still missing the ad libraries. If the error actually specified which Java class wasn’t found, it might’ve been a good clue.
I’ve messed with settings, tried updating and downgrading plugins, removing and re-adding ad libraries, but sadly I don’t seem to be making any progress with this at the moment.
I went on a deep dive and removed just about every plugin we had, even most of the Unity packages for things like notifications and in-app purchases to see what, if any, were modifying the gradle file to remove Android libraries.
But the configurations.implementation still exists.
