Firebase builds and Android - (ios references and python missing from Android images)

[SilkyPants]

Context
Due to the nature of some projects - it might be quicker to combine and download a single image that contains both the Android and iOS modules. This would also help address builds that require the use of the UnityEditor.iOS.Extensions.Xcode reference (which seems to be a common thing if you integrate with Firebase/Google libraries)

googlesamples/unity-jar-resolver#412

Suggested solution
Create a new image with the module type mobile or possibly android-ios if this would mean there is less work for the remainder of the build scripts. This image would contain both the Android and iOS modules installed.

Considered alternatives
None I can think of

Additional details
Ideally, this would not be required, but due to the later versions of Unity being stricter with the reference inclusion this silently breaks apps as the required libraries are disabled during the build process. It appears Google is working on their issue, though I could see a benefit for a combined base image in the future for cross mobile platform builds.

Assembly 'Assets/ExternalDependencyManager/Editor/Google.IOSResolver_v1.2.164.dll' will not be loaded due to errors:
Unable to resolve reference 'UnityEditor.iOS.Extensions.Xcode'. Is the assembly missing or incompatible with the current platform?
Reference validation can be disabled in the Plugin Inspector.

Assembly 'Assets/Firebase/Editor/Firebase.Crashlytics.Editor.dll' will not be loaded due to errors:
Unable to resolve reference 'UnityEditor.iOS.Extensions.Xcode'. Is the assembly missing or incompatible with the current platform?
Reference validation can be disabled in the Plugin Inspector.

Assembly 'Assets/Firebase/Editor/Firebase.Editor.dll' will not be loaded due to errors:
Unable to resolve reference 'UnityEditor.iOS.Extensions.Xcode'. Is the assembly missing or incompatible with the current platform?
Reference validation can be disabled in the Plugin Inspector.

[webbertakken]

it might be quicker to combine and download a single image that contains both the Android and iOS modules.

For very small projects or a very slow data connection this could be true - in which case there is the solution of self-hosted runners. We have consciously chosen against this because it eliminates our preference for parallelization. The bottleneck is usually not in the downloading of the image (which would even be substantially bigger in the suggested approach) but the build process itself - especially concerning CPU time. Parallelisation is important for by far most cases that we know of.

Please note that in the opening post the problem is not described clearly - just the solution. This makes it harder to think along. Could you please elaborate on the problem we're trying to solve here? Is it about later versions of Unity being stricter with the reference inclusion or Due to the nature of some projects?

some projects

Could you speak further for the actual use case that would make this preferable?

[SilkyPants]

Sorry for the confusion - I was not meaning to build both iOS and Android in the same build step, and agree that a preference for parallelization is definitely worth while.

The specific issue I have faced is when including the Firebase libraries I get the above errors. This is something that Google is working on trying to solve, but from what I have managed to find it could be tricky or not possible - as the required preprocessor commands to exclude the iOS libraries cannot be run for their final package. This is where I was mentioning 'some projects' and on reading back should have been a lot clearer - this is a problem with any Android project that includes an external library with iOS code included, where I might see a lot of them including the Firebase or other Google libraries.

The current workaround for this issue is to include the iOS module in the Unity - regardless of if it is being used. This looks to be an issue with the newer 2020 versions of Unity as pointed out in this comment, where I can only assume in the earlier versions it might have been a silent warning instead of an error.

For us - I am still looking into this issue on the side, as there may be other workarounds as well as getting myself more familiar with the Dockerimage process. Will update if I find anything worth while

[SilkyPants]

I may have found a workaround for now - buried in the plugin settings you can Disable the validation (didn't understand that error properly to see that option).

The next problem seems to be that python is not included in the Android image? Is this to be expected?

Unable to find command line tool python required for Firebase Android resource generation.
python is required to generate the Firebase Android resource file google-services.xml from Assets/GoogleService-Info.plist. Without Firebase Android resources, your app will fail to initialize.
python was distributed with each Firebase Unity SDK plugin, was it deleted?

I have also updated the issue to better reflect the issue that's happening here, for others to find.

EDIT: Added image to illustrate the option

[davidmfinol]

Currently, python is only included on webGL and linux-IL2CPP.
Maybe we should also include python on Android in order to support this?

[jklingsporn]

Yes, please. However if there is a known workaround, I'd give it a try.

[SilkyPants]

Argh - I fogot to update >.<

I did have a bit of a workaround (at least for my situation). It's pretty much installing Python before running my build scripts with apt install python -y. This is working fine for us at the moment, though having python inluded in the Docker image would be great.

[webbertakken]

Currently, python is only included on webGL and linux-IL2CPP.
Maybe we should also include python on Android in order to support this?

Accepting a PR for this.

[dharmeshmp]

I am facing the same issue in Unity 2021.2.8 and Image version 0.16

Before upgrade the version its working fine for me
Older version is 2021.1.20f1 and Image version 0.15

[mastef]

Would be amazing to have a simple symlink in the docker images. Either installing python 2 with RUN apt install python -y or simply adding RUN ln -s /usr/bin/python3 /usr/bin/python in the end

[webbertakken]

Can we assume that by now it's ok to go with Python 3 only and use your second suggestion?

We're open to PRs with your suggested changes.

[davidmfinol]

We went with adding RUN ln -s /usr/bin/python3 /usr/bin/python for certain platforms.

Do you all think this issue is resolved, or should we try to expand and add python to all target platforms like @mastef suggested in #152 ?