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.
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… )
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.
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?