buildozer: _python_bundle does not exist...this not looks good, all python recipes should have this folder, should we expect a crash soon?

@RobertFlatt @misl6 there seems to be a Kivy release planned for yesterday (2023-10-21 according to “kivy schedule” calendar). If you want to make a release of Kivy and/or Buildozer please do not wait for me go ahead 😃

Do not worry, the release has been postponed, as we’re waiting for an update from a dependency.

(And we likely need to change our 2.3.0 plans in term of features, as we may need to move some features to a major release)

1. I tried clean, changed project directory hello to hello.git, then build. Build completed and libpybundle.so was good.

2. I’m not a venv user (I use a WSL instance), so I don’t have any experience. I did have a user once tell me that a strange issue was due creating a venv one Python major version , then updating the system Python to a new major version. This is as far as I know a rumor, and outside my experience.

I went back to your build and checked the file sizes in the same was as I did for my build (above)

>~/ex/yyy/compass>unzip -l bin/* | grep private
      195  1981-01-01 01:01   assets/private.tar
>~/ex/yyy/compass>unzip -l bin/* | grep pybundle
       60  1981-01-01 01:01   lib/arm64-v8a/libpybundle.so
       60  1981-01-01 01:01   lib/armeabi-v7a/libpybundle.so
       60  1981-01-01 01:01   lib/x86/libpybundle.so
       60  1981-01-01 01:01   lib/x86_64/libpybundle.so

Which confirms your diagnosis of the symptoms. But a cause eludes me.

Here I use:

• JDK version is as specified in Buildozer install instructions (17).
• Clang/LLVM version is that provided by NDK, by default the NDK version is specified by p4a, and p4a version by buildozer.spec

What is wrong here???

Since you are the only person to report this, it looks like it must be something site specific, but on 3 OS!!!

Do all the machines have the same .bashrc ?
Edit: can you share the result of a bash env ?

Attached is the build log from my Ubuntu build. log.txt

On Ubuntu, using the “compass” directory provided, I tried:

>buildozer android debug
>unzip -l bin/* | grep pybundle
  8774602  1981-01-01 01:01   lib/arm64-v8a/libpybundle.so
  8593957  1981-01-01 01:01   lib/armeabi-v7a/libpybundle.so
  8891747  1981-01-01 01:01   lib/x86/libpybundle.so
  9065868  1981-01-01 01:01   lib/x86_64/libpybundle.so
>unzip -l bin/* | grep private
    36714  1981-01-01 01:01   assets/private.tar

Which does not match the reported symptoms.

Please post the result of doing exactly the same on MacOS.

The differences are:

• Ubuntu/MacOS
• user specified environments.

I can’t see anything odd in the provided log (which does not mean that there is nothing odd there)

I can’t replicate the issue, and I know nothing about Buildozer on MacOS so I suggest asking here https://discord.gg/8MwBmCDg

In your post include the above results, and your equivalent results.