Unity Editor does not recognize installed plaforms

Hi,
I updated to Unity 6000.0.60f1 due to the security gap in previous versions. I am running on Linux Mint 22.2 (all packages up to date).
Since then, the editor shows in the Build Profiles only Linux as installed platforms. All other platforms are greyed out. However, I have installed Anroid and Windows as well through Unity Hub.
The Build Profiles is giving the notification that the other platforms have to be installed, which they are already.
I removed Unity and installed it again but the result was the same.
All worked fine for Unity 6000.0.58

Hope some has a clue what’s going on…Thanks :wink:

EDIT: Same for a fresh created project.

EDIT2: Works on Win11 without any issues. Problems remains on Linux.

With regards,
Sebastian

Hi @Noxlor
This is a known issue and we’ll have a patch out in the next day or two. You can downgrade to Unity Hub 3.14.3 if this is blocking you.

​We appreciate your patience while we prepare this patch for deployment.

@Noxlor I’m tagging to notify you that the issues related to Android module installation have been resolved in the latest Beta patch 3.15.2-beta.1.

Here is the post announcing this beta version: Now Available: Unity Hub 3.15.0 - #33 by toddbunity

If you visit Settings β†’ Advanced β†’ Channels in Unity Hub and select Beta, you can take advantage of the fix immediately.

Hi,
I can confirm that with Unity Hub 3.15.2 and upgraded Editor to 6000.0.61f1 the issue is fixed.
Thanks for patching this such quick.

Regards

The issue is fixed for ubuntu LTS. I know that it is the supported distro, so it is all fine, but the regression persists for some other distros, like fedora 43, debian 13 for example, where on 3.14.2 the module recognition works fine, with 3.15.2 it is still bugged. Just letting you know, because I have tested on those 2 distros, and noticed it is still there.

Hi @CampaNulla,

Could you please post your logs here if possible? Additionally, could you file a bug report using the Hub bug reporter and share the ticket number here?

Most likely the extract command is failing silently on non-Ubuntu systems. The module is packaged as a .pkg file, which makes extraction difficult to implement reliably across multiple operating systems and distributions.

Logs from multiple users will help us narrow down the issue and provide a fix in the next major release.

Workaround for now: You can manually extract the .pkg file into the PlaybackEngines directory. You can find the correct package for your Unity version here.

Thank you for your patience!

Hi I’ve uninstalled both hub and the editor, reinstalled and confirmed that the issue persists.
Here are the logs:
info-log.zip (130.4 KB)

I’ve also made a bug report using the Hub bug reporter: CASE IN-125088

Here are also some screenshots of what’s happening:


Details about my setup:
Hub version: 3.15.2 (28523eb)
Editor version: 6.2 (6000.2.12f1)
Arch Linux (Omarchy)

I’ve also tried the workaround, I couldn’t get it working. I’m not fully sure I’ve understood where to extract the package. My current folder path looks like this:
/home/baran/Unity/Hub/Editor/6000.2.12f1/Editor/Data/PlaybackEngines/UnitySetup-Android-Support-for-Editor-6000.2.12f1
Here’s where I’ve got the .pkg file from: Unity 6000.2.12f1

Also I should mention the Hub did create some files in the PlaybackEngines folder.
Here’s the folder structre:

/home/baran/Unity/Hub/Editor/6000.2.12f1/Editor/Data/PlaybackEngines
β”œβ”€β”€ AndroidPlayer
β”‚   β”œβ”€β”€ NDK
β”‚   β”‚   └── ...
β”‚   β”œβ”€β”€ OpenJDK
β”‚   β”‚   └── ...
β”‚   β”œβ”€β”€ Payload~
β”‚   └── SDK
β”‚        └── ...
β”œβ”€β”€ AndroidPlayer.zip
β”œβ”€β”€ LinuxStandaloneSupport
β”‚   β”œβ”€β”€ Bee
β”‚   β”‚   └── ...
β”‚   β”œβ”€β”€ LinuxPlayerBuildProgram.Data.dll
β”‚   β”œβ”€β”€ LinuxPlayerBuildProgram.Data.pdb
β”‚   β”œβ”€β”€ LinuxPlayerBuildProgram.exe
β”‚   β”œβ”€β”€ LinuxPlayerBuildProgram.pdb
β”‚   β”œβ”€β”€ modules.asset
β”‚   β”œβ”€β”€ UnityEditor.LinuxStandalone.Extensions.dll
β”‚   β”œβ”€β”€ UnityEditor.LinuxStandalone.Extensions.pdb
β”‚   └── Variations
β”‚        └── ...
└── UnitySetup-Android-Support-for-Editor-6000.2.12f1
    β”œβ”€β”€ Distribution
    β”œβ”€β”€ PlugIns
    β”œβ”€β”€ Resources
    β”‚   └── ...
    └── TargetSupport.pkg.tmp
          └── ...

Same here.
Artix Linux (OpenRC, KDE Plasma), bash.

Seems like Unity honestly needs to do more testing before releasing new versions…

Downgrading Hub to 3.14.1 and reinstalling Unity 6000.2.13f1 (using AUR) to commit c7358b56a0288f85a67af1859a649583a9491262 like this seems to work:

git clone https://aur.archlinux.org/unityhub.git
cd unityhub
git checkout c7358b56a0288f85a67af1859a649583a9491262 # hub 3.14.1
makepkg -si

Hub 3.14.1

Test compilation was successful (used 3D Mobile template)

Hub 3.15.2

Here’s a quick tree of my AndroidPlayer PlackbackEngine:

~/Unity/Hub/Editor/6000.2.13f1/Editor/Data/PlaybackEngines/AndroidPlayer$ tree -L 2
.
β”œβ”€β”€ NDK
β”‚   β”œβ”€β”€ build
β”‚   β”œβ”€β”€ CHANGELOG.md
β”‚   β”œβ”€β”€ meta
β”‚   β”œβ”€β”€ ndk-build
β”‚   β”œβ”€β”€ ndk-gdb
β”‚   β”œβ”€β”€ ndk-lldb
β”‚   β”œβ”€β”€ ndk-stack
β”‚   β”œβ”€β”€ ndk-which
β”‚   β”œβ”€β”€ NOTICE
β”‚   β”œβ”€β”€ NOTICE.toolchain
β”‚   β”œβ”€β”€ prebuilt
β”‚   β”œβ”€β”€ python-packages
β”‚   β”œβ”€β”€ README.md
β”‚   β”œβ”€β”€ shader-tools
β”‚   β”œβ”€β”€ simpleperf
β”‚   β”œβ”€β”€ source.properties
β”‚   β”œβ”€β”€ sources
β”‚   β”œβ”€β”€ toolchains
β”‚   └── wrap.sh
β”œβ”€β”€ OpenJDK
β”‚   β”œβ”€β”€ bin
β”‚   β”œβ”€β”€ conf
β”‚   β”œβ”€β”€ include
β”‚   β”œβ”€β”€ legal
β”‚   β”œβ”€β”€ lib
β”‚   β”œβ”€β”€ NOTICE
β”‚   └── release
β”œβ”€β”€ Payload~
└── SDK
    β”œβ”€β”€ build-tools
    β”œβ”€β”€ cmake
    β”œβ”€β”€ cmdline-tools
    β”œβ”€β”€ platforms
    β”œβ”€β”€ platform-tools
    └── tools

24 directories, 13 files

Hi,

I have filed a bug report for Debian 13 with attached logs just in case, IN-125192
And here is the log:
info-log.zip (11.5 KB)

I know it was the same on Fedora 43 when I did a very short system test, and the repro steps were identical to what posters above already detailed.

As a workaround I’m using Hub 3.14.3 and keeping it from self updating. It adds the modules without problems on every distro I’ve tested.

Hey folks,

We found the issue and fixed it! I’m pushing hard to have the fix included in an upcoming patch, but right now it is included in Hub 3.16.0.

Thanks again for your patience and logs/reports!

Edit: A quick explanation of the issue…
We use 7zip to extract the .pkg files. On Ubuntu (where we test and develop) the binary detects the nested gzip Payload and extracts it in a single step. On other distros, this doesn’t happen.

Here’s roughly what we’re dealing with:
Ubuntu: [name].pkg β†’ TargetSupport.pkg.tmp/Payload~ (cpio) β†’ AndroidPlayer
Other distros: [name].pkg β†’ TargetSupport.pkg.tmp/Payload (gzip) β†’ TargetSupport.pkg.tmp/Payload~ (cpio) β†’ AndroidPlayer

I added an extra check and now we handle the 3-step extract on non-Ubuntu distros. I’ve also internally asked whether the Linux modules can instead be distributed a tar.gz or similar in the future.

NOTE: reminder Unity and the Hub team do not officially support non-Ubuntu distros. I spent time after hours researching and fixing this.

Hi,

Thanks for solving the issue for all us distro hoppers! It was a sneaky devil by the looks of it. Ubuntu just likes to do stuff differently then the rest sometimes, oh snap.

If only all the issues were solved this fast, we would be already in a different universe.

Cheers!

Thanks for fixing it even though it isn’t officially supported! It was a bummer to see I can’t build to Android from Linux, made me consider switching to other open source game engines. Good to see I can keep working on my projects.

Also, on another note, thanks for being this quick with it! First reply in 24h and fix in 5 days is amazing to see, and definitely has improved the chance of me recommending Unity to a friend!

Beta with the fix is rolling out now!

Thank you all for the reports! Give me a shout if you see any further issues

Thanks, good thread and info here, I had a similar problem with Windows build from Linux. Info and end fix here for others, and/or if this wasn’t also addressed in latest fix already:

Kubuntu 25.10 (So basically Ubuntu 25.10)
UnityHub 3.15.2
Unity Editor 6000.2.15f1 (with Linux and Win build support)

UnityHub showed Linux build support and Windows build support installed.
Unity Editor showed Linux build support, but not Windows. No errors or anything.

Looking at ~/Unity/Hub/Editor/6000.2.15f1/Editor/Data/PlaybackEngines/WindowsStandaloneSupport/ there was only one (cpio) file: Payload~

I just extracted this manually in the dir and it worked fine: $ cpio -iv < Payload~

Hi @haexed

Yes this is addressed in the latest beta!

Hi, is there any way to install the beta on arch-based linux distros? (pacman)
I didn’t find one yet, unfortunately. If not, is there another way I can get around this issue? Really need Android Build Support.
Thank you!

Writing this here in case anybody has the same problem:
There is a Flatpak of Unity Hub, which is an older version (3.12.1), which works fine for building for android or meta quest. I consider this as a workaround, until the fixes for this problem are in the next non-beta release

Hi @Leetsch2002

I’m not super familiar with arch linux, but you should be able to download the unstable RPM from here: Index of hub-rpm-prod-local/unity/unstable/unityhub_x86_64

I believe Arch has the tools to unpackage and install RPMs

I can confirm that the 3.15.3 fix is working on Debian 13. Unity Hub adds modules and they are recognised by the editor. Thanks again for the fix!