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

sdkmanager --update called even if required tools already installed #1336

Closed
OrangeDog opened this issue Jun 29, 2021 · 4 comments
Closed

sdkmanager --update called even if required tools already installed #1336

OrangeDog opened this issue Jun 29, 2021 · 4 comments

Comments

@OrangeDog
Copy link

OrangeDog commented Jun 29, 2021

Versions

  • Python: 3.6.8
  • OS: CentOS 7.9.2009
  • Buildozer: 1.2.0

Description

When running an Android build, sdkmanager --update is always called, which downloads the latest versions of SDK and NDK. This happens even if the app is configured to use an older version that is already installed. This uses up a considerable amount of time and disk space.

The build will then always fail, because p4a doesn't work for NDK >=22.
kivy/python-for-android#2391

buildozer.spec

Command:

buildozer android release

Spec file:

# (int) Target Android API, should be as high as possible.
android.api = 30

# (int) Minimum API your APK will support.
android.minapi = 24

# (str) Android NDK version to use
android.ndk = 19c

# (int) Android NDK API to use. This is the minimum API your app will support, it should usually match android.minapi.
android.ndk_api = 24

Logs

[0m�[1;30m# Run '/var/lib/jenkins/node/tools/android-sdk/tools/bin/sdkmanager --sdk_root=/var/lib/jenkins/node/tools/android-sdk --update'�[0m
�[0m�[1;30m# Cwd /var/lib/jenkins/node/tools/android-sdk�[0m
Warning: Mapping new ns http://schemas.android.com/repository/android/common/02 to old ns http://schemas.android.com/repository/android/common/01
Warning: Mapping new ns http://schemas.android.com/repository/android/generic/02 to old ns http://schemas.android.com/repository/android/generic/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/addon2/02 to old ns http://schemas.android.com/sdk/android/repo/addon2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/repository2/02 to old ns http://schemas.android.com/sdk/android/repo/repository2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/sys-img2/02 to old ns http://schemas.android.com/sdk/android/repo/sys-img2/01
Loading package information...                                                  
Loading local repository...                                                     
Warning: Mapping new ns http://schemas.android.com/repository/android/common/02 to old ns http://schemas.android.com/repository/android/common/01
Warning: Mapping new ns http://schemas.android.com/repository/android/generic/02 to old ns http://schemas.android.com/repository/android/generic/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/addon2/02 to old ns http://schemas.android.com/sdk/android/repo/addon2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/repository2/02 to old ns http://schemas.android.com/sdk/android/repo/repository2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/sys-img2/02 to old ns http://schemas.android.com/sdk/android/repo/sys-img2/01
...       
[===                                    ] 10% Computing updates...              
[===                                    ] 10% Installing NDK                    
[===                                    ] 10% Downloading android-ndk-r22b-linux
@xandro0777
Copy link

apparently you build with jenkins? Any chance it clears its workspace on every build attempt?

@OrangeDog
Copy link
Author

@xandro0777 yes, but the Android tools aren't installed in the workspace, otherwise every build would take hours.

@xandro0777
Copy link

@OrangeDog: You are perhaps hitting an issue that is fixed by #801 ? If it works for you leave a comment there.

I think a bit more should be cached in the per user .buidlozer, it should be avoidable to download a complete python and cython universe every times a new project is started - #1363.

@Julian-O
Copy link
Contributor

This is being closed, but not forgotten. It has been consolidated into issue #1727.

@Julian-O Julian-O closed this as not planned Won't fix, can't repro, duplicate, stale Oct 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants