1. Hey! Guest! The 35th GMC Jam will take place between November 28th, 12:00 UTC - December 2nd, 12:00 UTC. Why not join in! Click here to find out more!
    Dismiss Notice

Android GMS2 different Minimum SDK showing up

Discussion in 'GameMaker Studio 2 Community Tech Support' started by emicarra, Jun 8, 2019.

  1. emicarra

    emicarra Member

    Joined:
    Jul 2, 2017
    Posts:
    41
    Hello, i just moved my GMS1.4 project to GMS2, when i export to android an error message appears in the output saying "android 14 is unsupported, using minimum supported version android 16.", the thing is the minimum SDK shown in "Game Options - Android" is 16, so why does it say android 14 is unsupported?, here's the full error:

    Android NDK: android-14 is unsupported. Using minimum supported version android-16.
    Android NDK: WARNING: APP_PLATFORM android-16 is higher than android:minSdkVersion 14 in ./AndroidManifest.xml.

    Also i opened GMS2 AndroidManifest.xml in Android Studio but i couldn't find "android:minSdkVersion 14" anywhere.
    This error happens for around 1 minute and then sometimes it compiles fine and sometimes it doesn't.

    Screenshot:
    [​IMG]

    Thanks for your help
     
  2. FrostyCat

    FrostyCat Member

    Joined:
    Jun 26, 2016
    Posts:
    4,607
    Chances are that you have an extension that still depends on API 14, and that is injecting the requirement into the manifest. Upgrade it or remove it.
     
  3. emicarra

    emicarra Member

    Joined:
    Jul 2, 2017
    Posts:
    41
    Thanks for the response, that's probably it but there's a problem, i deleted the extension and also cleaned the cache but when i compiled it still shows API 14. So i checked the output and "on one part it says Attempting to call extension function with no extensions loaded isSignedIn on class GooglePlayServicesExtension".
    It seems the extension wasn't completly removed from the project, maybe i should open a new thread for this issue.
    I also checked in the project folder/extensions, but the folder is empty.
    Thanks for your help
     
  4. rIKmAN

    rIKmAN Member

    Joined:
    Sep 6, 2016
    Posts:
    4,646
    Try removing the extension from the 1.4 project, cleaning the cache and saving it as a new project.
    Then import that "clean" project into GMS2.

    It may still be getting referenced somewhere from the import process, although it obviously shouldn't happen and still might not work but is worth a try.
     
  5. SnortySnoopy

    SnortySnoopy Member

    Joined:
    Apr 25, 2018
    Posts:
    214
    Correct me if I'm wrong. I also see it all the time when I build an .apk, but rarely will my build fail unless I made a mistake somewhere within the IDE. I think the issue why we see it is simply because we don't have "android-14" folder (and its content) in our ndk-bundle folder. In my case, I can clearly tell I don't have in %Android\Sdk\ndk-bundle\platforms\%. The ones that I do have matches what I did downloaded from Android Studio's SDK Manager. I'm not going to download 14 because I always set my app min target to 19 (Android 4.4). So my guess is, if you want to try making it go away; maybe launch the SDK Manager, and download Android 4.0 (Ice Cream Sandwich) API 14 Revision 4. However (disclaimer) please don't hold me accountable if the message doesn't go away. But don't worry, downloading it won't cause any harm except use up some of your harddisk space. :p
     
    Last edited: Jun 9, 2019
  6. darthjaiz

    darthjaiz Member

    Joined:
    Nov 5, 2019
    Posts:
    1
    Fixed mine by saving my project to a new project (save as project) save to a different folder.
     
  7. chirpy

    chirpy Member

    Joined:
    Oct 6, 2016
    Posts:
    156
    Exporting and reimporting the project didn't help me. Even an empty project shows the messages:

    Android NDK: android-14 is unsupported. Using minimum supported version android-16.
    Android NDK: WARNING: APP_PLATFORM android-16 is higher than android:minSdkVersion 14 in ./AndroidManifest.xml.

    Is there anything else I could try to do?
     
  8. rIKmAN

    rIKmAN Member

    Joined:
    Sep 6, 2016
    Posts:
    4,646
    What version of the NDK are you using?
    The setup article recommends NDK 20 so if you are using a different version I'd uninstall the current version and install v20, point GMS2 to it and try again with a fresh empty project.
     
  9. chirpy

    chirpy Member

    Joined:
    Oct 6, 2016
    Posts:
    156
    I'm using v20, following recommended settings here: https://help.yoyogames.com/hc/en-us/articles/115001368727-Setting-Up-For-Android
    I also uninstalled Android Studio and did a clean install, with my .gradle .android .AndroidStudio3.5 folders removed, still no luck.

    Code:
    ClangExeLocation=D:\Android\sdk\ndk\20.0.5594570\toolchains\llvm\prebuilt\windows-x86_64\bin\clang++.exe
    Using NDKDir = D:\Android\sdk\ndk\20.0.5594570
    Using PlatformDir = D:\Android\sdk\ndk\20.0.5594570\platforms\android-29
    Using ARMToolChain = D:\Android\sdk\ndk\20.0.5594570\toolchains\arm-linux-androideabi-4.9\prebuilt\windows-x86_64
    saving file Y:/ndk-test_160F49A_YYC\ndk-test.droid
    Android NDK: android-14 is unsupported. Using minimum supported version android-16.
    Android NDK: WARNING: APP_PLATFORM android-16 is higher than android:minSdkVersion 14 in ./AndroidManifest.xml. NDK binaries will *not* be compatible with devices older than android-16.
    See https://android.googlesource.com/platform/ndk/+/master/docs/user/common_problems.md for more information.
    I had been able to build, and my uploaded builds to Google Play Console looks fine, listing correct API levels 16+, and Target SDK 29.
    So I'm leaning towards letting it go. Hopefully it's harmless. =(

    By the way, the build success results also ends with:
    Code:
    Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0.
    Use '--warning-mode all' to show the individual deprecation warnings.
    See https://docs.gradle.org/5.1.1/userguide/command_line_interface.html#sec:command_line_warnings
     
    Last edited: Nov 7, 2019

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice