Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERR_UNSUPPORTED_API_LEVEL: Unsupported API level: 23 #257

Closed
crowbait opened this issue Sep 20, 2022 · 1 comment · Fixed by #349
Closed

ERR_UNSUPPORTED_API_LEVEL: Unsupported API level: 23 #257

crowbait opened this issue Sep 20, 2022 · 1 comment · Fixed by #349
Labels

Comments

@crowbait
Copy link

crowbait commented Sep 20, 2022

Version:

1.7.0

Description:

ERR_UNSUPPORTED_API_LEVEL: Unsupported API level: 23
Without clear reason, native-run seems to have stopped supporting my MinSKD. I have not knowingly changed the variables.gradle or project settings in android studio...
What I did do was get rid of some AVD devices I didn't use anymore.

Command Output:

Since I normally use npx cap run android, which doesn't support the --verbose flag, I don't know how to produce a meaningful output. Help would be appreciated. If I run native-run android --verbose, the following is printed, which hints at some missing setup which I guess is normally handled by capacitor:

  native-run:android:utils:sdk:resolveSDKRoot Looking for $ANDROID_SDK_ROOT +1ms
  native-run:android:utils:sdk:resolveSDKRoot Looking at following directories: [ 'C:\\Users\\fabia\\AppData\\Local\\Android\\Sdk' ] +1ms
  native-run:android:utils:sdk:resolveSDKRoot Using C:\Users\fabia\AppData\Local\Android\Sdk +4ms
  native-run:android:utils:sdk:resolveEmulatorHome Looking for $ANDROID_EMULATOR_HOME +0ms
  native-run:android:utils:sdk:resolveEmulatorHome Looking at $HOME/.android +0ms
  native-run:android:utils:sdk:resolveEmulatorHome Using $HOME/.android/ at C:\Users\fabia\.android +1ms
  native-run:android:utils:sdk:resolveAVDHome Looking for $ANDROID_AVD_HOME +0ms
  native-run:android:utils:sdk:resolveAVDHome Looking at $HOME/.android/avd +0ms
  native-run:android:utils:sdk:resolveAVDHome Using $HOME/.android/avd/ at C:\Users\fabia\.android\avd +1ms
  native-run Caught fatal error: CLIException [Error]: --app is required
  native-run     at Object.run (F:\ownCloud\traxx.li\Stormbase Development\RandomChat\node_modules\native-run\dist\android\run.js:30:15)
  native-run     at async Object.run (F:\ownCloud\traxx.li\Stormbase Development\RandomChat\node_modules\native-run\dist\android\index.js:19:5)
  native-run     at async Object.run (F:\ownCloud\traxx.li\Stormbase Development\RandomChat\node_modules\native-run\dist\index.js:20:13) {
  native-run   code: 'ERR_BAD_INPUT',
  native-run   exitCode: 1,
  native-run   data: undefined
  native-run } +0ms

SDK Info:

PS F:\ownCloud\traxx.li\Stormbase Development\RandomChat> npx native-run android --sdk-info 
SDK Location:         C:\Users\fabia\AppData\Local\Android\Sdk
AVD Home:             C:\Users\fabia\.android\avd

API Level:            33
Packages:             Android SDK Platform 33  platforms;android-33  2
                      Sources for Android 33  sources;android-33  1
                      Sources for Android 33  sources;android-33-ext3  1
(!) Missing Packages: Google Play Intel x86 Atom System Image  system-images;android-33;google_apis_playstore;x86  /.+/

API Level:            32
Packages:             Android SDK Platform 32  platforms;android-32  1
                      Sources for Android 32  sources;android-32  1
(!) Missing Packages: Google Play Intel x86 Atom System Image  system-images;android-32;google_apis_playstore;x86  /.+/

API Level:            31
Packages:             Android SDK Platform 31  platforms;android-31  1
                      Sources for Android 31  sources;android-31  1
(!) Missing Packages: Google Play Intel x86 Atom System Image  system-images;android-31;google_apis_playstore;x86  /.+/

API Level:            30
Packages:             Google Play Intel x86 Atom System Image  system-images;android-30;google_apis_playstore;x86  9
(!) Missing Packages: Android SDK Platform 30  platforms;android-30

API Level:            29
Packages:             Android SDK Platform 29  platforms;android-29  5
(!) Missing Packages: Google Play Intel x86 Atom System Image  system-images;android-29;google_apis_playstore;x86  /.+/

API Level:            28
Packages:             Android SDK Platform 28  platforms;android-28  6
(!) Missing Packages: Google Play Intel x86 Atom System Image  system-images;android-28;google_apis_playstore;x86  /.+/

API Level:            27
Packages:             Google Play Intel x86 Atom System Image  system-images;android-27;google_apis_playstore;x86  3
(!) Missing Packages: Android SDK Platform 27  platforms;android-27

API Level:            23
Packages:             Android SDK Platform 23  platforms;android-23  3
                      Sources for Android 23  sources;android-23  1

API Level:            22
Packages:             Android SDK Platform 22  platforms;android-22  2
                      Sources for Android 22  sources;android-22  1

API Level:            21
Packages:             Android SDK Platform 21  platforms;android-21  2
                      Sources for Android 21  sources;android-21  1


Tools:

Android Emulator  emulator  31.3.10
Android SDK Build-Tools 28.0.3  build-tools;28.0.3  28.0.3
Android SDK Build-Tools 29.0.2  build-tools;29.0.2  29.0.2
Android SDK Build-Tools 30.0.2  build-tools;30.0.2  30.0.2
Android SDK Build-Tools 30.0.3  build-tools;30.0.3  30.0.3
Android SDK Build-Tools 31-rc3  build-tools;31.0.0-rc3  31.0.0
Android SDK Build-Tools 33  build-tools;33.0.0  33.0.0
Android SDK Command-line Tools (latest)  cmdline-tools;latest  7.0
Android SDK Platform-Tools  platform-tools  33.0.3
Android SDK Tools  tools  26.1.1
SDK Patch Applier v4  patcher;v4  1
@crowbait
Copy link
Author

crowbait commented Sep 20, 2022

Update: if I have a physical device connected, npx cap run android does work. It does not present a list of devices (although the emulator is running), but chooses the physical device automatically and succeeds in deploying the app.
I can also run the app directly from android studio on the AVD, if I set the configuration to app instead of android:
image

This however does not fix npx cap run-behaviour.

It is as if native-run fails because it just doesn't recognize the AVD...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant