Android Resolver is not working

Hi

It works fine on Unity 2021.1 but on 2021.2 alpha the google play resolver, which is required by many packages, it´s failing with this error

Exception thrown when initializing PlayServicesResolver: System.Reflection.AmbiguousMatchException: Ambiguous match found

Anyone managed to get it to work?

This is a bug and has been reported to Google like days ago. Cutting edge versions of Unity will always have issues. I tried multiple older versions of External Dependency Manager but same spam errors popped up.

Seems like for us early adopters, using an older version of Unity for production work is the only way for now.

1 Like

I was the one reporting it to google.
The issue is that we can’t test anything on Unity because unless your project doesn’t do anything serious on Android, you won’t be able to even compile without the Google Jar resolver. Amazed nobody detected this on any project. I wonder what kind of test projects Unity has on Android that doesn’t include anything standard in almost every project (facebook sdk, firebase sdk, google mobile sdk… )

2 Likes

My guess they don’t really have any kind of test projects that are close to reality. Otherwise we wouldn’t have seen releases so consistently broken. And I’m not talking about Unity Editor itself but various packages like Addressables. For example, the currently “verified” version for 2020.3 LTS has critical bug that prevents loading any bundles if you have runtime properties in your loadpath… (which you do, by default).

They do have projects. I used to be a beta and even an alpha tester years ago and provided my full project to keep it on their system. They asked for people to volunteer their projects so Unity would fail to release if it didn’t pass with those projects.

Obviously this was years ago and it seems they don’t do this anymore then. Because I can´t think of any real-life project would compile without errors on Android.

2 Likes

bump

what’s the current state of this bug? has google or unity said anything about this bug? is it planned to be fixed?

@creat327 do you have a link to the report? I can’t see any related open issue in the admob Github

found this but they don’t mention the android resolver, only the IOS one

in my case clicking the android “force resolve” or “resolve” doesn’t show the usual progress bar or any sign that the resolving was done.

and getting a never ending spam of :

AmbiguousMatchException: Ambiguous match found.
1 Like

The Android resolver was fixed on the 166 update, that´s why you won’t find it on the list of pending issues. Only the iOS one is failing now.

1 Like

thank you, i downloaded the 1.2.166 jar resolver from github and now its working.

I’m still encountering this issue in 2021.2.7f1… It occurs in one of my projects, but not any of the others… Does anyone know what could be causing this?

1 Like

Also getting this still in Unity 2021.2.6f1 I have downloaded the jar resolver 1.2.169 and still causing the issue

jus use api30

  • Install Ads Mediation from Package Manager.
  • Restart Unity.

These steps worked for me. I hope it’s work for you too.

what about im using unity ads