@TakuyaBabuya Was this Editor version added to the Hub using the Locate button?
As @Kustuk pointed out, these are the menu options shown in that case.
If the Editor version was installed using Install Editor, you should see the Add modules button in the Manage list.
Hi @Kustuk
If the install works on 3.12 and not 3.15 that’s certainly a regression. Could you file a bug report for the “Something went wrong” error and post the ticket number here. I’ll make sure we look into it ASAP.
Thanks!
Hi, sure.
Thanks so much for looking into it.
Hey everyone,
We have new beta release for 3.15.3 rolling out now. This is a small one to address an issue reported with installation of Android modules on non-Ubuntu distros.
December 2, 2025
Bug fixes & improvements
Any news about the possibility to remove modules from HUB, strange that you can install them but not remove them 
Still failing on Fedora 43 when installing Android build tools etc. iOS installs fine as does the editor.
Only way to have it working is to downgrade to 3.12.1
It also fail to install android NDK module in macOS
Hi @grenangen
I just tested Fedora 43 and I’m unable to reproduce. I was able to install the latest 6.2 and Android build tools. Note that I’m using the latest beta from the unstable RPM channel.
If you still have some issues after installing the latest beta, could file a bug and post the ticket number here. Thanks!
Hi @Oscar-Tsang
I just tested on MacOS 26.1 with Unity 6.3 and the Android tools, and I’m unable to reproduce.
If you continue to have issues installing the module, could you please file a bug and reply with the ticket here. Thanks!
Hi @AndreaGalet
I’ll ask the team and see what we can do! Do be aware this might be non-trivial. Some module installers drop files in multiple locations in the Editor directory. We (the Hub) don’t necessarily know all of these locations!
Hi, I’m unsure if this is the best way to contact the Unity Hub team, but here I go!
I’m the maintainer of the Unity Hub package for the Linux distribution NixOS, and somewhat recently I’ve noticed a change with how the debian repository is structured. Previously, each version of the Unity Hub .deb had a different file with a consistent name in the debian repository. However, now all the new versions are named with the same file… see 3.15.2 in https://hub-dist.unity3d.com/artifactory/hub-debian-prod-local/dists/stable/main/binary-amd64/Packages. This breaks the mechanism that our package manager used to fetch specific versions of the package, as well as the mechanism used to update the package. Is it possible for this change to be reverted, or if there’s a new mechanism for downloading specific versions of the .deb distribution, that’d be greatly appreciated!
Nixpkgs issue: unityhub: downloads on debian repo are no longer separated by version · Issue #464494 · NixOS/nixpkgs · GitHub
Hello @huantianad,
Thank you for bringing this to our attention. You are correct, during the update of our packaging and publishing infrastructure in the 3.15.x series, an issue was introduced that affected the versioning format for Linux packages.
This issue has been resolved in the development of the 3.16 series. Moving forward, new Linux package releases will adhere to the following consistent naming convention:
UnityHubSetup-[version]-[arch].[ext]
We sincerely apologize for any confusion or inconvenience this may have caused. We are always open to community suggestions, and we welcome any further feedback you may have regarding our Linux releases or the Hub in general.
Thank you again for your patience and valuable input!
I’d like to report a bug, on 3.15.2 cli installing editor + modules is only picking up the first module from the list, ex:
"/Applications/Unity Hub.app/Contents/MacOS/Unity Hub" -- --headless install -v 6000.2.10f1 -c 7134d7685e5d -a arm64 -m android ios
Will only install android, on the previous 3.14.3 it correctly install all the modules.
But repeating the -m command multiple times works on 3.15.2 it seems, but this not the way it’s documented:
"/Applications/Unity Hub.app/Contents/MacOS/Unity Hub" -- --headless install -v 6000.2.10f1 -c 7134d7685e5d -a arm64 -m android -m ios
Also a couple of feedbacks in order to be possible to make a fully autonomous install using the hub possible:
--childModules no or similar to not prompt “Would you also like to install the child modules …”, I have to use expect to automatic force it.Invalid key: The GraphQL query at the field at `UnityRelease:2022.2.0a18.label` has a selection set, but no key could be generated for the data at this field.
You have to request `id` or `_id` fields for all selection sets or create a custom `keys` config for `UnityReleaseLabel`.
Entities without keys will be embedded directly on the parent entity. If this is intentional, create a `keys` config for `UnityReleaseLabel` that always returns null.
Thanks
Hey folks,
We just updated the thread with release notes for 3.15.3. The update is rolling out now!
This is the last update of the year and the final 3.15.x release. We tried to fix as many issues as possible to send off 2025!
Just checked the latest version, just in case - “something went wrong” problem is still there.
Hi @Kustuk
We’re still looking into your issue. The QA team has been unable to reproduce so far. I’ll be taking a closer look in the coming days. If I find a fix it won’t be until 3.16
Thank you for you patience!
Hi @Kustuk,
I’ve found the cause of your issue! As a temporary fix, could you change your Editor install directory to not be the root of your C drive?
This is an interesting edge case. Our validator that checks for a valid destination before running the installer has a bug when it tries to ensure the destination path exists. It trips up on C:\ and tries to create C:\, which unsurprisingly explodes. We’ve branched off 3.16 recently, and I’ll make sure to slip in a fix for this.
Thanks for sending in the report!
On hub version 3.15.4, the install problem is fixed, but the alias in /PlaybackEngines/AndroidPlayer/NDK/toolchains/llvm/prebuilt/darwin-x86_64/bin/, clang* pointed to wrong file, not point to clang-18 ( I only see it), so when build in android, it fail to build, it need to copy from old version unity NDK files to replace the toolchains folder. In order to build success.
Hi @Oscar-Tsang
Are you installing the Editor on a volume? We had this issue reported that we’ll have fixed in 3.16:
What I want to know now is when you will support custom project templates. Every time I want to try new features and start a new project, I have to repeatedly add and remove packages.