Cloud build cannot download Api level 33 which is now required for play store.
Local builds work fine in Unity 2021.3.15f1 just like the cloud build is configured.
(See specific links on how I got Android 33 going, near the bottom)
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.
Here was how I brought up Unity2020.3.41 and the Android SDK 31 on October 30, 2022 (edited on August 23, 2023 to include Android SDK 33…):
Android Gradle errors and other related stuff:
Turns out cloud build is improperly detecting the selected SDK in the project properties
Manually setting 33 in the configuration properties on cloud build makes the build work
Without manually setting it, it launches the build on a machine with version 30
[2023-10-14T16:39:45Z - Unity] Detected outdated SDK Platform version 30.0.0 when the min version is 33.0.0
Accrued a couple $ in build charges screwing with cloud build this week. Neat.
1 Like
Considering the globality of Google Play’s requirement for things like SDK 33+ and 64bit and whatnot, this decision seems like quite a fail on the part of Cloud build.
I haven’t been on Cloud’s dash since its early days but sometimes that sort of thing is buried deep in a website configuration setting somewhere.
Oh yeah, now I remember: Cloud used to be one price to use with Mercurial / SVN but they charged extra if you used git… that was “okay, peace out, I don’t have time for people who think that is somehow a good business model.”