[Buildozer] Transformer une application en APK

Version imprimable

21/02/2026, 22h07
toitoinebzh

[Buildozer] Transformer une application en APK
Bonjour,

J'ai développé une petite application en Python/Kivy qui fonctionne correctement sur mon pc et j'aimerai la transformer en APK pour la tester sur mon téléphone.

J'ai suivi les explications données sur internet en apportant quelques modifications au fichier spec
Code:

1 2 buildozer init buildozer android debug deploy run
la compilation se lance bien mais j'aboutis sur un message d'erreur que je n'arrive pas à débloquer

Code:

WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available.

Un peu plus de détails ici
https://bin.infini.fr/?ca46701fb0c9e...CLqtxGKo6pPrH2

je suis preneur d'un coup de main

merci
21/02/2026, 23h13
fred1599
Hello,

Il manque le paquet requis pour SSL sur votre système je pense: libssl-dev
Sur debian/ubuntu, installez ces paquets,
Code:

1 2 sudo apt update sudo apt install build-essential libssl-dev zlib1g-dev libffi-dev libreadline-dev libbz2-dev libsqlite3-dev
Après nettoyez et compilez à nouveau,
Code:

1 2 buildozer android clean buildozer android debug
22/02/2026, 12h51
toitoinebzh

Merci fred1599,
J'ai installé ces paquets et cela m'a débloqué la situation, la compilation n'aboutit cependant pas, j'ai ce message d'erreur

Citation:

Starting a Gradle Daemon, 1 incompatible and 2 stopped Daemons could not be reused, use --status for details

j'ai vu cette erreur décrite ailleurs sur le web, mais sans apporter de solution

voilà un peu plus de détails

Citation:

[DEBUG]: Create directory src/main/assets
Compiling '/document/toto/CochonsApp/.buildozer/android/app/main.py'...
Compiling '/document/toto/CochonsApp/.buildozer/android/app/fonctions.py'...
Compiling '/document/toto/CochonsApp/.buildozer/android/app/sitecustomize.py'...
[DEBUG]: Remove directory and subdirectory /tmp/p4a-extra-env-c4zctbr1
[DEBUG]: Remove directory and subdirectory src/main/res
[INFO]: Detected highest available build tools version to be 37.0.0-rc1
[DEBUG]: -> running gradlew clean assembleDebug
[DEBUG]: Starting a Gradle Daemon, 1 incompatible and 2 stopped Daemons could not be reused, use --status for details
[DEBUG]:
[DEBUG]: [Incubating] Problems report is available at: file:///document/toto/CochonsApp/.buildozer/android/platform/build-arm64-v8a_armeabi-v7a/dists/Cochons/build/reports/problems/problems-report.html
[DEBUG]:
[DEBUG]: FAILURE: Build failed with an exception.
[DEBUG]:
[DEBUG]: * Where:
[DEBUG]: Build file '/document/toto/CochonsApp/.buildozer/android/platform/build-arm64-v8a_armeabi-v7a/dists/Cochons/build.gradle' line: 30
[DEBUG]:
[DEBUG]: * What went wrong:
[DEBUG]: A problem occurred evaluating root project 'Cochons'.
[DEBUG]: > Value is null
[DEBUG]:
[DEBUG]: * Try:
[DEBUG]: > Run with --stacktrace option to get the stack trace.
[DEBUG]: > Run with --info or --debug option to get more log output.
[DEBUG]: > Run with --scan to get full insights.
[DEBUG]: > Get more help at https://help.gradle.org.
[DEBUG]:
[DEBUG]: Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
[DEBUG]:
[DEBUG]: You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
[DEBUG]:
[DEBUG]: For more on this, please refer to https://docs.gradle.org/8.14.3/userg..._line_warnings in the Gradle documentation.
[DEBUG]:
[DEBUG]: BUILD FAILED in 13s

Exception in thread background thread for pid 3662:
Traceback (most recent call last):
File "/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
self.run()
File "/usr/lib/python3.11/threading.py", line 975, in run
self._target(*self._args, **self._kwargs)
File "/document/toto/lib/python3.11/site-packages/sh.py", line 1642, in wrap
fn(*rgs, **kwargs)
File "/document/toto/lib/python3.11/site-packages/sh.py", line 2647, in background_thread
handle_exit_code(exit_code)
File "/document/toto/lib/python3.11/site-packages/sh.py", line 2338, in fn
return self.command.handle_command_exit_code(exit_code)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/document/toto/lib/python3.11/site-packages/sh.py", line 823, in handle_command_exit_code
raise exc
sh.ErrorReturnCode_1:

RAN: /document/toto/CochonsApp/.buildozer/android/platform/build-arm64-v8a_armeabi-v7a/dists/Cochons/gradlew clean assembleDebug

STDOUT:
Starting a Gradle Daemon, 1 incompatible and 2 stopped Daemons could not be reused, use --status for details

[Incubating] Problems report is available at: file:///document/toto/CochonsApp/.buildozer/android/platform/build-arm64-v8a_armeabi-v7a/dists/Cochons/build/reports/problems/problems-report.html

FAILURE: Build failed with an exception.

* Where:
Build file '/document/toto/CochonsApp/.buildozer/android/platform/build-arm64-v8a_armeabi-v7a/dists/Cochons/build.gradle' line: 30

* What went wrong:
A problem occurred evaluating root project 'Cochons'.
> Value is null

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.14.3/userg..._line_warnings in the Gradle documentation.

BUILD FAILED in 13s

STDERR:

[INFO]: STDOUT (last 20 lines of 33):
* What went wrong:
A problem occurred evaluating root project 'Cochons'.
> Value is null

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.14.3/userg..._line_warnings in the Gradle documentation.

BUILD FAILED in 13s

[INFO]: STDERR:
22/02/2026, 13h09
fred1599
Citation:

Code:

[INFO]: Detected highest available build tools version to be 37.0.0-rc1

Les versions -rc (Release Candidate) sont instables et souvent incompatibles avec les scripts Gradle par défaut de Buildozer, ce qui provoque l'erreur Value is null.

Ouvrez votre fichier buildozer.spec et recherchez la ligne concernant la version des outils de construction. Par défaut, elle est souvent commentée ou laissée vide.
Code:

1 2 3 android.build_tools_version = 34.0.0 android.api = 34 android.ndk = 25b
Ensuite
Code:

1 2 buildozer android clean buildozer -v android debug
22/02/2026, 15h14
toitoinebzh

Je viens de générer un nouveau fichier spec (bluidozer init) et je n'ai pas apporté de modifications sur la version des outils à utiliser (ligne restée commentée).

Citation:

[DEBUG]: clang-14: error: no such file or directory: 'jnius/jnius.c'

Citation:

[DEBUG]: creating build/temp.linux-x86_64-3.11/jnius
[DEBUG]: /home/antoine/.buildozer/android/platform/android-ndk-r25b/toolchains/llvm/prebuilt/linux-x86_64/bin/clang -target aarch64-linux-android21 -fomit-frame-pointer -march=armv8-a -fPIC -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -target aarch64-linux-android21 -fomit-frame-pointer -march=armv8-a -fPIC -I/document/toto/CochonsApp/.buildozer/android/platform/build-arm64-v8a_armeabi-v7a/build/other_builds/python3/arm64-v8a__ndk_target_21/python3/Include -DANDROID -I/home/antoine/.buildozer/android/platform/android-ndk-r25b/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/include -I/document/toto/CochonsApp/.buildozer/android/platform/build-arm64-v8a_armeabi-v7a/build/python-installs/Cochonss/arm64-v8a/include/python3.1 -fPIC -I/document/toto/CochonsApp/.buildozer/android/platform/build-arm64-v8a_armeabi-v7a/build/other_builds/hostpython3/desktop/hostpython3/Include -I/document/toto/CochonsApp/.buildozer/android/platform/build-arm64-v8a_armeabi-v7a/build/other_builds/hostpython3/desktop/hostpython3/native-build -c jnius/jnius.c -o build/temp.linux-x86_64-3.11/jnius/jnius.o
[DEBUG]: clang-14: error: no such file or directory: 'jnius/jnius.c'
[DEBUG]: clang-14: error: no input files
[DEBUG]: error: command '/home/antoine/.buildozer/android/platform/android-ndk-r25b/toolchains/llvm/prebuilt/linux-x86_64/bin/clang' failed with exit code 1
Exception in thread background thread for pid 84905:
Traceback (most recent call last):
File "/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
self.run()
File "/usr/lib/python3.11/threading.py", line 975, in run
self._target(*self._args, **self._kwargs)
File "/document/toto/lib/python3.11/site-packages/sh.py", line 1641, in wrap
fn(*rgs, **kwargs)
File "/document/toto/lib/python3.11/site-packages/sh.py", line 2569, in background_thread
handle_exit_code(exit_code)
File "/document/toto/lib/python3.11/site-packages/sh.py", line 2269, in fn
return self.command.handle_command_exit_code(exit_code)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/document/toto/lib/python3.11/site-packages/sh.py", line 869, in handle_command_exit_code
raise exc
sh.ErrorReturnCode_1:

RAN: /document/toto/CochonsApp/.buildozer/android/platform/build-arm64-v8a_armeabi-v7a/build/other_builds/hostpython3/desktop/hostpython3/native-build/python3 setup.py build_ext -v

STDOUT:
warning: [options] bootstrap class path not set in conjunction with -source 8
1 warning
running build_ext
building 'jnius' extension
creating build
creating build/temp.linux-x86_64-3.11
creating build/temp.linux-x86_64-3.11/jnius
/home/antoine/.buildozer/android/platform/android-ndk-r25b/toolchains/llvm/prebuilt/linux-x86_64/bin/clang -target aarch64-linux-android21 -fomit-frame-pointer -march=armv8-a -fPIC -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -target aarch64-linux-android21 -fomit-frame-pointer -march=armv8-a -fPIC -I/document/toto/CochonsApp/.buildozer/android/platform/build-arm64-v8a_armeabi-v7a/build/other_builds/python3/arm64-v8a__ndk_target_21/python3/Include -DANDROID -I/home/antoine/.buildozer/android/platform/android-ndk-r25b/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/include -I/document/toto/CochonsApp/.buildozer/android/platform/build-arm64-v8a_armeabi-v7a/build/python-installs/Cochonss/arm64-v8a/include/python3.1 -fPIC -I/document/toto/CochonsApp/.buildozer/android/platform/build-arm64-v8a_armeabi-v7a/build/other_builds/hostpython3/desktop/hostpython3/Include -I/document/toto/CochonsApp/.buildozer/android/platform/build-arm64-v8a_armeabi-v7a/build/other_builds/hostpython3/desktop/hostpython3/native-build -c jnius/jnius.c -o build/temp.linux-x86_64-3.11/jnius/jnius.o
clang-14: error: no such file or directory: 'jnius/jnius.c'
clang-14: error: no input files
error: command '/home/antoine/.buildozer/android/platform/android-ndk-r25b/toolchains/llvm/prebuilt/linux-x86_64/bin/clang' failed with exit code 1

STDERR:

[INFO]: pyjnius first build failed (as expected)
[INFO]: Running cython where appropriate
[INFO]: Cythonize jnius/jnius.pyx
[DEBUG]: -> running python3 -cimport sys; from Cython.Compiler.Main import setuptools_main; sys.exit(setuptools_main()); ./jnius/jnius.pyx
[DEBUG]: warning: jnius/jnius.pyx:102:0: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
[DEBUG]:
[DEBUG]: Error compiling Cython file:
[DEBUG]: ------------------------------------------------------------
[DEBUG]: ...
[DEBUG]: score += 10
[DEBUG]: continue
[DEBUG]:
[DEBUG]: if r == 'S' or r == 'I':
[DEBUG]: if isinstance(arg, int) or (
[DEBUG]: (isinstance(arg, long) and arg < 2147483648)):
[DEBUG]: ^
[DEBUG]: ------------------------------------------------------------
[DEBUG]: jnius/jnius_utils.pxi:323:37: undeclared name not builtin: long
Exception in thread background thread for pid 84935:
Traceback (most recent call last):
File "/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
self.run()
File "/usr/lib/python3.11/threading.py", line 975, in run
self._target(*self._args, **self._kwargs)
File "/document/toto/lib/python3.11/site-packages/sh.py", line 1641, in wrap
fn(*rgs, **kwargs)
File "/document/toto/lib/python3.11/site-packages/sh.py", line 2569, in background_thread
handle_exit_code(exit_code)
File "/document/toto/lib/python3.11/site-packages/sh.py", line 2269, in fn
return self.command.handle_command_exit_code(exit_code)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/document/toto/lib/python3.11/site-packages/sh.py", line 869, in handle_command_exit_code
raise exc
sh.ErrorReturnCode_1:

RAN: /document/toto/bin/python3 '-cimport sys; from Cython.Compiler.Main import setuptools_main; sys.exit(setuptools_main());' ./jnius/jnius.pyx

STDOUT:
warning: jnius/jnius.pyx:102:0: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310

Error compiling Cython file:
------------------------------------------------------------
...
score += 10
continue

if r == 'S' or r == 'I':
if isinstance(arg, int) or (
(isinstance(arg, long) and arg < 2147483648)):
^
------------------------------------------------------------
jnius/jnius_utils.pxi:323:37: undeclared name not builtin: long

STDERR:

Traceback (most recent call last):
File "<frozen runpy>", line 198, in _run_module_as_main
File "<frozen runpy>", line 88, in _run_code
File "/document/toto/CochonsApp/.buildozer/android/platform/python-for-android/pythonforandroid/toolchain.py", line 1256, in <module>
main()
File "/document/toto/CochonsApp/.buildozer/android/platform/python-for-android/pythonforandroid/entrypoints.py", line 18, in main
ToolchainCL()
File "/document/toto/CochonsApp/.buildozer/android/platform/python-for-android/pythonforandroid/toolchain.py", line 685, in __init__
getattr(self, command)(args)
File "/document/toto/CochonsApp/.buildozer/android/platform/python-for-android/pythonforandroid/toolchain.py", line 104, in wrapper_func
build_dist_from_args(ctx, dist, args)
File "/document/toto/CochonsApp/.buildozer/android/platform/python-for-android/pythonforandroid/toolchain.py", line 163, in build_dist_from_args
build_recipes(build_order, python_modules, ctx,
File "/document/toto/CochonsApp/.buildozer/android/platform/python-for-android/pythonforandroid/build.py", line 504, in build_recipes
recipe.build_arch(arch)
File "/document/toto/CochonsApp/.buildozer/android/platform/python-for-android/pythonforandroid/recipe.py", line 1031, in build_arch
self.build_cython_components(arch)
File "/document/toto/CochonsApp/.buildozer/android/platform/python-for-android/pythonforandroid/recipe.py", line 1056, in build_cython_components
self.cythonize_build(env=env)
File "/document/toto/CochonsApp/.buildozer/android/platform/python-for-android/pythonforandroid/recipe.py", line 1104, in cythonize_build
self.cythonize_file(env, build_dir, join(root, filename))
File "/document/toto/CochonsApp/.buildozer/android/platform/python-for-android/pythonforandroid/recipe.py", line 1093, in cythonize_file
shprint(python_command, "-c"
File "/document/toto/CochonsApp/.buildozer/android/platform/python-for-android/pythonforandroid/logger.py", line 167, in shprint
for line in output:
File "/document/toto/lib/python3.11/site-packages/sh.py", line 915, in next
self.wait()
File "/document/toto/lib/python3.11/site-packages/sh.py", line 845, in wait
self.handle_command_exit_code(exit_code)
File "/document/toto/lib/python3.11/site-packages/sh.py", line 869, in handle_command_exit_code
raise exc
sh.ErrorReturnCode_1:

RAN: /document/toto/bin/python3 '-cimport sys; from Cython.Compiler.Main import setuptools_main; sys.exit(setuptools_main());' ./jnius/jnius.pyx

STDOUT:
warning: jnius/jnius.pyx:102:0: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310

Error compiling Cython file:
------------------------------------------------------------
...
score += 10
continue

if r == 'S' or r == 'I':
if isinstance(arg, int) or (
(isinstance(arg, long) and arg < 2147483648)):
^
------------------------------------------------------------
jnius/jnius_utils.pxi:323:37: undeclared name not builtin: long

STDERR:

je vais maintenant reternter en imposant la version des outils à utiliser (android.build_tools_version n'est pas dispo dans le fichier spec)
22/02/2026, 16h47
toitoinebzh

même résultat en spécifiant la version des outils
22/02/2026, 19h47
fred1599

Cette nouvelle erreur est différente de la précédente, bien qu'elle survienne au même stade du processus. Il s'agit d'un conflit de version entre Cython (le compilateur qui transforme le code Python en C) et Pyjnius (la bibliothèque Kivy qui permet de communiquer avec Android/Java).

L'erreur critique est : undeclared name not builtin: long.

Le type long existait en Python 2 mais a été supprimé en Python 3 (où tout est int). Récemment, Cython est passé en version 3.0, laquelle est beaucoup plus stricte et refuse désormais l'utilisation du mot-clé long.

Imposez votre version cython dans le fichier buildozer.spec

Code:

requirements = python3, kivy, Cython==0.29.33

Assurez-vous d'utiliser Java 17. Avec l'API 34 et Gradle 8+, Java 11 ou 8 peuvent provoquer des erreurs de type Unsupported class file major version.
Vérification : java -version. Si besoin : sudo apt install openjdk-17-jdk.
22/02/2026, 21h38
toitoinebzh

bon, c'est vraiment le parcours du combattant :)
j’aboutis au même message d'erreur

merci pour les explications, je comprends mieux le message d'erreur maintenant

concernant les versions des logiciels, je suis bon sur java mais pas sur gradle, je vais voir si je peux facilement monter en version

Citation:

$ gradle --version
openjdk version "17.0.18" 2026-01-20
OpenJDK Runtime Environment (build 17.0.18+8-Debian-1deb12u1)
OpenJDK 64-Bit Server VM (build 17.0.18+8-Debian-1deb12u1, mixed mode, sharing)

------------------------------------------------------------
Gradle 4.4.1
------------------------------------------------------------

Build time: 2012-12-21 00:00:00 UTC
Revision: none

Groovy: 2.4.21
Ant: Apache Ant(TM) version 1.10.13 compiled on February 6 2023
JVM: 17.0.18 (Debian 17.0.18+8-Debian-1deb12u1)
OS: Linux 6.1.0-42-amd64 amd64

$ java --version
openjdk 17.0.18 2026-01-20
OpenJDK Runtime Environment (build 17.0.18+8-Debian-1deb12u1)
OpenJDK 64-Bit Server VM (build 17.0.18+8-Debian-1deb12u1, mixed mode, sharing)
22/02/2026, 22h25
toitoinebzh

je viens de mettre à jour gradle en passant par sdkman, mais le résultat reste le même :(

Citation:

$ gradle -v

------------------------------------------------------------
Gradle 9.3.1
------------------------------------------------------------

Build time: 2026-01-29 14:15:01 UTC
Revision: 44f4e8d3122ee6e7cbf5a248d7e20b4ca666bda3

Kotlin: 2.2.21
Groovy: 4.0.29
Ant: Apache Ant(TM) version 1.10.15 compiled on August 25 2024
Launcher JVM: 17.0.18 (Debian 17.0.18+8-Debian-1deb12u1)
Daemon JVM: /usr/lib/jvm/java-17-openjdk-amd64 (no Daemon JVM specified, using current Java home)
OS: Linux 6.1.0-42-amd64 amd64
22/02/2026, 23h10
fred1599
Buildozer télécharge et utilise son propre "Gradle Wrapper" (gradlew) à l'intérieur du dossier caché .buildozer, vous venez de télécharger une version gradle incompatible.

Pour que la compilation réussisse, vous devez impérativement forcer Buildozer à utiliser des versions de composants qui "se parlent" correctement.

Puisque Buildozer a déjà tenté de construire l'environnement avec les mauvaises versions, il a stocké des fichiers corrompus. Il faut forcer Buildozer à tout retélécharger correctement.
Code:

1 2 3 buildozer android clean buildozer -v android debug
Je veux bien revoir votre fichier buildozer.spec
23/02/2026, 19h57
toitoinebzh

très bien, j'ai désinstallé sdkman et le gradle associé
le résultat reste le même

voilà le fichier spec
https://bin.infini.fr/?c3c3dd258da05...D5KsUD97wK8PBE
25/02/2026, 07h44
MPython Alaplancha

Bonjour.
As-tu préalablement réussi à compiler un hello world ?
25/02/2026, 20h31
toitoinebzh

Bonjour,

Mon application est très basique (c'est mon premier programme avec kivy).

Je viens de tester un simple hello world en kivy avec un fichier spec "vierge" (généré avec "buildozer init"), le résultat est le même