Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We’re making changes to the Unity Runtime Fee pricing policy that we announced on September 12th. Access our latest thread for more information!
    Dismiss Notice
  3. Dismiss Notice

Question [2019.4.40f1] How to get "recommended JDK/SDK Tools/Android NDK" that is officially supported?

Discussion in 'Editor & General Support' started by nina32176, May 29, 2023.

  1. nina32176


    Jun 27, 2018
    Hello friends,
    I just installed unity, version as in title.
    In the past, I used 2017 for years but it is no longer supported.
    After installing the new version. I am unable to build my project for Android.
    Here are my prefs:
    I was searching for solution but everything seems to say that I must "install them with unity", but unity installation dialog just let me tick "Android platform" and I ticked that, and there is still no JDK/SDK/nothing.

    To be clear, the paths given on prefs are empty... AndroidPlayer directory:
    See? Nothing here.

    I don't get it, how should I install recommended stuff? Thanks!
  2. Hexolenn


    Dec 27, 2021
    I had the same problem as well and after I re-installed with the correct modules it worked correctly.

    To chech if you have installed them correctly you can go and check from unity hub installs tab
    Ekran görüntüsü 2023-05-29 164140.png

    After that go to the settings button(Cogwheel) of the isntallation that you are using. And select add modules Ekran görüntüsü 2023-05-29 164156.png

    Lastly check if you downloaded the right things for a mobile platform those being:
    Android Build Support
    Android SDK & NDK Tools
    Ekran görüntüsü 2023-05-29 164216.png

    If you cannot see these you can add them as modules or re-install the unity version with these modules.

    If you have these modules installed and still have problems I am sorry but I don't have an answer for you
  3. nina32176


    Jun 27, 2018
    Well, thank you for reply, but I searched and rechecked again and as you can see below, I have no "add modules" entry:
    I can only run again UnityDownloadAssistant-2019.4.40f1.exe , where I got:

    but i did that, and still nothing
  4. Hexolenn


    Dec 27, 2021
    The first time this happened to me I had the same problem as well I couldn't see the add modules tab as well but after re-isntalling it appeared for me. But that could be because I had a newer version of unity as you can see I use 2021.3.25f1.

    Maybe you can try going for a higher version as well because while installing It showed me bot android build support and those modules I talked about.

    As you can see if you go to the install editor at the top and select the latest versions it shows me the modules

    You can try to update your version in the install editor but if you cannot see modules in it while downloading.
  5. Kurt-Dekker


    Mar 16, 2013
    Unity2019 is not any more supported than Unity2017 is.

    As Hex said above, select a version that is still supported or you'll be inhibited from doing meaningful game dev while you attempt to fix what might be unfixable.

    In any case, Unity2020.3.40f1 is the oldest version of Unity that has the Android 12+ audio crash bug fixed.

    ISSUES RELATED TO UPGRADING PROJECTS (eg, changing to a higher Unity version)

    Upgrading to a later version of Unity is a one-way process. Any project that has been updated should NEVER be reverted to an earlier version of Unity because this is expressly not supported by Unity. Doing so exposes your project to internal inconsistencies and breakage that may actually be impossible to repair.

    If you want to upgrade to a newer version of Unity, do not even consider it until you have placed your project fully under proper source control. This goes double or triple for non-LTS (Tech Stream) versions of Unity3D, which can be extremely unstable compared with LTS.

    Once you have source-controlled your project then you may attempt a Unity upgrade. Immediately after any attempted upgrade you should try to view as much of your project as possible, with a mind to looking for broken animations or materials or any other scripting errors or runtime issues.

    After an upgrade you should ALWAYS build to all targets you contemplate supporting: iOS and Android can be particularly finicky, and of course any third party libraries you use must also "play nice" with the new version of Unity. Since you didn't write the third party library, it is up to you to vet it against the new version to make sure it still works.

    If there are issues in your testing after upgrading Unity, ABANDON the upgrade, revert your project in source control and be back where you were pre-upgrade with the earlier version of Unity.

    Obviously the less you test after the upgrade the more chance you will have of an undiscovered critical issue.

    This risk of upgrading is entirely on you and must be considered whenever you contemplate a Unity version upgrade.

    Do not upgrade "just for fun" or you may become very unhappy.


    I'm sorry you've had this issue. Please consider using proper industrial-grade enterprise-qualified source control in order to guard and protect your hard-earned work.

    Personally I use git (completely outside of Unity) because it is free and there are tons of tutorials out there to help you set it up as well as free places to host your repo (BitBucket, Github, Gitlab, etc.).

    You can also push git repositories to other drives: thumb drives, USB drives, network drives, etc., effectively putting a complete copy of the repository there.

    As far as configuring Unity to play nice with git, keep this in mind:

    I usually make a separate repository for each game, but I have some repositories with a bunch of smaller test games.

    Here is how I use git in one of my games, Jetpack Kurt:

    Using fine-grained source control as you work to refine your engineering:

    Share/Sharing source code between projects:

    Setting up an appropriate .gitignore file for Unity3D:

    Generally the ONLY folders you should ever source control are:


    NEVER source control Library/ or Temp/ or Logs/
    NEVER source control anything from Visual Studio (.vs, .csproj, none of that noise)

    Setting git up with Unity (includes above .gitignore concepts):

    It is only simple economics that you must expend as much effort into backing it up as you feel the work is worth in the first place. Digital storage is so unbelievably cheap today that you can buy gigabytes of flash drive storage for about the price of a cup of coffee. It's simply ridiculous not to back up.

    If you plan on joining the software industry, you will be required and expected to know how to use source control.

    "Use source control or you will be really sad sooner or later." - StarManta on the Unity3D forum boards
    nina32176 likes this.
  6. nina32176


    Jun 27, 2018
    Thank you for your detailed response. I appreciate it.

    First I will say that I am forced by Google Play to update my game. They delete all games like crazy.

    Every new Unity version breaks my game even more. I already lost legacy particle system (last supported in 2017) and had to resolve cursor lock bug.

    Can you please tell me more about "Android audio crash"? What is that? Will I run into it in my 3D basic game?
  7. Kurt-Dekker


    Mar 16, 2013
    This was where I worked from:

    Specifically about 2019 no longer being supported, from the same thread above:

    There were more reported crashes in December 2022 (in the newer versions of Unity) but the Unity guy seemed to straighten the reports out by pointing out that the crash was not related to FMOD.

    Software is a living thing. If you don't regularly maintain any software it rapidly falls out of date.