at void com.unity3d.player.i.a(java.lang.String[ ], com.unity3d.player.IAssetPackManagerStatusQueryCallback) ((null):-1)
at void com.unity3d.player.PlayAssetDeliveryUnityWrapper.getAssetPackStates(java.lang.String[ ], com.unity3d.player.IAssetPackManagerStatusQueryCallback) ((null):-1)
at void com.unity3d.player.PlayAssetDeliveryUnityWrapper.getAssetPackState(java.lang.String, com.unity3d.player.IAssetPackManagerStatusQueryCallback) ((null):-1)
at boolean com.unity3d.player.UnityPlayerForActivityOrService.nativeRender() ((null):-2)
at boolean com.unity3d.player.K.handleMessage(android.os.Message) ((null):-1)
at void android.os.Handler.dispatchMessage(android.os.Message) (Handler.java:103)
at void android.os.Looper.loop() (Looper.java:228)
at void com.unity3d.player.N.run() ((null):-1)
Thank you for sharing this information - it definitely helps. It sounds like what you’re experiencing could be linked to a bug we are currently fixing. I’ll share the issue tracker if I can confirm it’s the same issue
keizof:
Self-reply: Deleting Assets/GooglePlayPlugins then installing 1.8.2 tarballs resolved the issue.
This worked for us - we’re using a third-party-plugin that handles the External-Dependency. Importing manually and removing some old refs and now everything is fine.
garundell_budge:
Is it on the Unity roadmap to port this Unity 2023 fix into LTS version of Unity 2021 and Unity 2022?
So the bug we believe to be linked to this issue, can be followed with this issue tracker. When it is fixed for 2023, it will be backported to both 2021 and 2022 LTS
JacobSimpsonUnity:
So the bug we believe to be linked to this issue, can be followed with this issue tracker. When it is fixed for 2023, it will be backported to both 2021 and 2022 LTS
Having the same issue on 2022.3.5f1, I guess the fix will rollout with 3.10 according to the issue you linked?
09-13 18:36:48.865 28045 28045 F DEBUG : Abort message: 'Throwing new exception 'No interface method getPackStates(Ljava/util/List;)Lcom/google/android/gms/tasks/Task; in class Lcom/google/android/play/core/assetpacks/AssetPackManager; or its super classes (declaration of 'com.google.android.play.core.assetpacks.AssetPackManager' appears in /data/app/~~ntQG_6WjCv_JqT6QAJuN9A==/{bundle.id}-oh96M3CpjpXTbzaZTzo_6A==/base.apk!classes2.dex)' with unexpected pending exception: java.lang.NoSuchMethodError: No interface method getPackStates(Ljava/util/List;)Lcom/google/android/gms/tasks/Task; in class Lcom/google/android/play/core/assetpacks/AssetPackManager; or its super classes (declaration of 'com.google.android.play.core.assetpacks.AssetPackManager' appears in /data/app/~~ntQG_6WjCv_JqT6QAJuN9A==/{bundle.id}-oh96M3CpjpXTbzaZTzo_6A==/base.apk!classes2.dex)
AlperDemirel-DEV:
Having the same issue on 2022.3.5f1, I guess the fix will rollout with 3.10 according to the issue you linked?
09-13 18:36:48.865 28045 28045 F DEBUG : Abort message: 'Throwing new exception 'No interface method getPackStates(Ljava/util/List;)Lcom/google/android/gms/tasks/Task; in class Lcom/google/android/play/core/assetpacks/AssetPackManager; or its super classes (declaration of 'com.google.android.play.core.assetpacks.AssetPackManager' appears in /data/app/~~ntQG_6WjCv_JqT6QAJuN9A==/{bundle.id}-oh96M3CpjpXTbzaZTzo_6A==/base.apk!classes2.dex)' with unexpected pending exception: java.lang.NoSuchMethodError: No interface method getPackStates(Ljava/util/List;)Lcom/google/android/gms/tasks/Task; in class Lcom/google/android/play/core/assetpacks/AssetPackManager; or its super classes (declaration of 'com.google.android.play.core.assetpacks.AssetPackManager' appears in /data/app/~~ntQG_6WjCv_JqT6QAJuN9A==/{bundle.id}-oh96M3CpjpXTbzaZTzo_6A==/base.apk!classes2.dex)
Looking at your log, the issue you’re facing is from the original Issue tracker I shared at the top of this thread. It’s been fixed on 2023.1+, but will not be backported to the version you’re using. Have you tried making a backup of your project, and upgrading to the latest 2023 version to check if this resolves your case?
Also to gather a better understanding about this particular issue, please could you describe how you were using Play Asset Delivery, and what android hardware and OS version you deployed to?
It’s the second year that i cannot build my game 
I have no idea why Unity after adding stuff don’t even know what they’re adding to their engine who’s the clever guy that made it? I’m on Unity 2021 and there’s no chance to update my game it’s literally 2 years that I could not update it.
Even without Play asset delivery there’s a play core dupplicates.
I would not to switch in 2023 since it has a billion issues. So what’s next?
mahito2932:
It’s the second year that i cannot build my game I have no idea why Unity after adding stuff don’t even know what they’re adding to their engine who’s the clever guy that made it? I’m on Unity 2021 and there’s no chance to update my game it’s literally 2 years that I could not update it.
Even without Play asset delivery there’s a play core dupplicates.
I would not to switch in 2023 since it has a billion issues. So what’s next?
Do you have an error log from your play core duplicate issue?
Log clearly say that there’s already google play core which cause a duplicate issues… I’m sure it happened because of in-app-purchase unity package since it’s already have core libraries… But google play core libraries they depend by admob and google play games. If I remove in app purchase package it’s building without any issues but my scripts depends on it I need to use in app purchase I don’t want to rewrite all the scripts and using google play billing which I think it’s already implemented in app purchase as well. This situation is during like for almost years and still no fix… So why implement something that prevent from using original open source made by google itself this is illegal.
It’s like saying you should use unity packages without using Google plugins but that’s not right event in terms of condition.
Detected “com.google.android.play:core” in Assets/Plugins/Android/mainTemplate.gradle. Assuming the dependency is already added.
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
There’s literally no way to fix it… Atleast open the source to be able to help you to fix that if even Unity couldn’t solve this in 5 years if not more
mahito2932:
Log clearly say that there’s already google play core which cause a duplicate issues… I’m sure it happened because of in-app-purchase unity package since it’s already have core libraries… But google play core libraries they depend by admob and google play games. If I remove in app purchase package it’s building without any issues but my scripts depends on it I need to use in app purchase I don’t want to rewrite all the scripts and using google play billing which I think it’s already implemented in app purchase as well. This situation is during like for almost years and still no fix… So why implement something that prevent from using original open source made by google itself this is illegal.
It’s like saying you should use unity packages without using Google plugins but that’s not right event in terms of condition.
Detected “com.google.android.play:core” in Assets/Plugins/Android/mainTemplate.gradle. Assuming the dependency is already added.
UnityEngine.GUIUtility:processEvent (int,intptr,bool&)
There’s literally no way to fix it… Atleast open the source to be able to help you to fix that if even Unity couldn’t solve this in 5 years if not more
I’m sorry your are experiencing this. I’ve taken a look and this is not a known issue. Please could you file a bug report with the repro project attached, and I’ll make sure it gets looked into. Thank you! 
keizof:
I’m getting the opposite problem on 2023.1.7f1 Intel (on M2 Mac with Rosetta, Ventura 13.3). Fail to find getPackStates in com/google/android/gms/tasks/Task.
Reproduced on Pixel 6a (Android 13) and P710 (Android 10). Let me know if any additional information helps.
at void com.unity3d.player.i.a(java.lang.String[ ], com.unity3d.player.IAssetPackManagerStatusQueryCallback) ((null):-1)
at void com.unity3d.player.PlayAssetDeliveryUnityWrapper.getAssetPackStates(java.lang.String[ ], com.unity3d.player.IAssetPackManagerStatusQueryCallback) ((null):-1)
at void com.unity3d.player.PlayAssetDeliveryUnityWrapper.getAssetPackState(java.lang.String, com.unity3d.player.IAssetPackManagerStatusQueryCallback) ((null):-1)
at boolean com.unity3d.player.UnityPlayerForActivityOrService.nativeRender() ((null):-2)
at boolean com.unity3d.player.K.handleMessage(android.os.Message) ((null):-1)
at void android.os.Handler.dispatchMessage(android.os.Message) (Handler.java:103)
at void android.os.Looper.loop() (Looper.java:228)
at void com.unity3d.player.N.run() ((null):-1)
In my case it was a specific combination of Unity and Play Asset Delivery versions - Unity 2020.3.48f1 and PAD 1.6.0 work successfully, while Unity 2020.3.36f1 and PAD 1.7.0-1.8.1 gave an error like yours.
edit: Resolved the problem. See bottom of my message.
After switching from Unity 2021 to 2022.3.16f1 I am now also getting this:
2024.01.09 12:53:40.572 26335 26421 Fatal zygote java_vm_ext.cc:534] JNI DETECTED ERROR IN APPLICATION: JNI NewStringUTF called with pending exception java.lang.NoSuchMethodError: No interface method getPackStates(Ljava/util/List;)Lcom/google/android/gms/tasks/Task; in class Lcom/google/android/play/core/assetpacks/AssetPackManager; or its super classes (declaration of ‘com.google.android.play.core.assetpacks.AssetPackManager’ appears in /data/app/com.xxx.yyy-LWYgVgwOLROyHc-Tudzlhg==/base.apk!classes4.dex)
2024.01.09 12:53:40.572 26335 26421 Fatal zygote java_vm_ext.cc:534] at void com.unity3d.player.i.a(java.lang.String[ ], com.unity3d.player.IAssetPackManagerStatusQueryCallback) ((null):-1)
2024.01.09 12:53:40.572 26335 26421 Fatal zygote java_vm_ext.cc:534] at void com.unity3d.player.PlayAssetDeliveryUnityWrapper.getAssetPackStates(java.lang.String[ ], com.unity3d.player.IAssetPackManagerStatusQueryCallback) ((null):-1)
2024.01.09 12:53:40.572 26335 26421 Fatal zygote java_vm_ext.cc:534] at void com.unity3d.player.PlayAssetDeliveryUnityWrapper.getAssetPackState(java.lang.String, com.unity3d.player.IAssetPackManagerStatusQueryCallback) ((null):-1)
2024.01.09 12:53:40.572 26335 26421 Fatal zygote java_vm_ext.cc:534] at boolean com.unity3d.player.UnityPlayer.nativeRender() ((null):-2)
2024.01.09 12:53:40.572 26335 26421 Fatal zygote java_vm_ext.cc:534] at boolean com.unity3d.player.UnityPlayer.-$$Nest$mnativeRender(com.unity3d.player.UnityPlayer) ((null):-1)
2024.01.09 12:53:40.572 26335 26421 Fatal zygote java_vm_ext.cc:534] at boolean com.unity3d.player.UnityPlayer$F$a.handleMessage(android.os.Message) ((null):-1)
2024.01.09 12:53:40.572 26335 26421 Fatal zygote java_vm_ext.cc:534] at void android.os.Handler.dispatchMessage(android.os.Message) (Handler.java:102)
2024.01.09 12:53:40.572 26335 26421 Fatal zygote java_vm_ext.cc:534] at void android.os.Looper.loop() (Looper.java:164)
2024.01.09 12:53:40.572 26335 26421 Fatal zygote java_vm_ext.cc:534] at void com.unity3d.player.UnityPlayer$F.run() ((null):-1)
Post #3 mentions using the 1.8.2 tarballs for PAD, but those are listed as 2023.1.0 (Beta) for Minimum Unity Version. So what other options are there to solve this problem if we want to upgrade to a current LTS version of Unity?
edit: I managed to get it to work following the advice of #15 . E.g. updating the google play review plugin. Note that I had to manually delete the GooglePlayPlugins folder in order not to run into problems by simply overwriting with the new version.
