Build works perfectly for Windows, but errors occur for Android

[superdoesthings]

I build my game for Windows, and it works perfectly. Then I try to build it for Android and it gives these errors. Any help would be appreciated!

[Kurt-Dekker]

How to troubleshoot build failures:

First, make a blank project with a single blank scene and prove that it builds successfully.

If the blank project does NOT build, go fix your Unity installation or your other tools, such as Android SDK, NDK, JDK, etc. It may even be necessary to change to a different version of Unity3D. It is generally best to stay with LTS versions of Unity3D.

Until you can build a blank project to the target platform, don’t fiddle with anything else.

Once you can build a blank project, now bisect the problem by bringing over parts of your current project and building it one subsystem at a time, perhaps stubbing things out that might trigger compiler errors.

Most often things that prevent building are third-party libraries such as Firebase.

Once you identify the subsystem, go to the documentation for it and make sure you are doing it correctly.

It may also be helpful to work through a tutorial or two for whatever subsystem is making the build fail.

Android build not building:

Recently (circa July 2022) there have been reports of Unity’s installer failing to install the Android Tools.

Can't build for Android

Latest Hub 3.2.0 in combination with Unity 2021.3.6 can't build for Android because there is a missing Tools folder inside *Editor\Data\PlaybackEngines\AndroidPlayer* so Unity can't find gradle. That folder is simply not created during the installation. The workaround is to copy the whole Tools folder from the previous Unity version or if you don't have the previous version then do what [mention|1j+oWeNEPCI6ejbN15sncw==] says in the post below .

Here was how I brought up Unity2020.3.41 and the Android SDK 31 on October 30, 2022:

.AAB Build Targeting API Level 33 on Unity 2021.3.8 with JDK 1.8.

Hey, coincidentally I just upgraded to Android SDK31 today… why not wait until nearly the last minute? It was a wild ride, took most of the day. Let me tell you what I did, what I found. First of all, I’m using Unity2020.3.41 (hereinafter referred to Unity*) because that’s all the further I need to go forward right now. I found that Unity* only accepts up to SDK30.0.3 tools, but will build using those tools and SDK31. Next I found that Android Studio will not install anything except Android …

Android Gradle errors and other related stuff:

Unity Gradle bug... please help

Fix:

[noping24]

The android build seems to be completely broken. It was working one day and stopped the next.

I have wasted a full week trying to resolve this. I cannot describe how frustrating this is.

[Kurt-Dekker]

@noping24

I cannot describe how frustrating this is.

There’s no need to because none of the people making the SDK software actually care.

It sounds brutal but it’s true. The SDK software is made by vast committees controlling vast teams comprised of people with skills ranging from barely-computer-literate interns up to brilliant senior engineers capable of anything.

The winning strategy I employ is a combination of:

• making builds frequently (including the moment I kick off a project, or if I add anything to it)

• getting good at searching the interwebs for the error messages

Lately I’ve had great luck using ChatGPT4 for getting more background on errors.

Just yesterday I suddenly had an the activity export error in Android, which is a required step for Android 12+ and which was not being asserted in one of my projects. Here’s what chat said:

https://chat.openai.com/share/2dc1a859-00a0-4a94-8e9e-a6c19db9acc7