You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a first attempt to build, Buildozer complains that "API target 21 is not available". However, after trying
for API 19, Buildozer seems to be able to pull down that API target itself; the build subsequently works.
(The first sed is because the current p4a stable branch doesn't know the python3 recipe, and the second sed is to work around 770.)
Spec file: just the current default.spec with those two sed commands run on it. (If a full copy is preferred, let me know, and I can paste it.)
Logs
…
[INFO]: Found Android API target in $ANDROIDAPI: 21
[INFO]: Available Android APIs are ()
[ERROR]: Build failed: Requested API target 21 is not available, install it with the SDK android tool.
# Command failed: /usr/bin/python3 -m pythonforandroid.toolchain create --dist_name=myapp --bootstrap=sdl2 --requirements=python3,kivy --arch armeabi-v7a --copy-libs --color=always --storage-dir="/home/cse/project/.buildozer/android/platform/build"
#
# Buildozer failed to execute the last command
# The error might be hidden in the log above this error
# Please read the full log, and search for it before
# raising an issue with buildozer itself.
# In case of a bug report, please add a full log with log_level = 2
However, if I go back to the defaults (which fails because of 770):
Versions
Description
On a first attempt to build, Buildozer complains that "API target 21 is not available". However, after trying
for API 19, Buildozer seems to be able to pull down that API target itself; the build subsequently works.
buildozer.spec
Commands:
(The first
sed
is because the currentp4a
stable branch doesn't know thepython3
recipe, and the secondsed
is to work around 770.)Spec file: just the current default.spec with those two
sed
commands run on it. (If a full copy is preferred, let me know, and I can paste it.)Logs
However, if I go back to the defaults (which fails because of 770):
and then go back to the non-defaults:
then the build works up until the issue described here.
The text was updated successfully, but these errors were encountered: