_python_bundle does not exist...this not looks good, all python recipes should have this folder, should we expect a crash soon? #1585
Comments
|
On Ubuntu, using the "compass" directory provided, I tried: Which does not match the reported symptoms. Please post the result of doing exactly the same on MacOS. The differences are:
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. |
Thanks @RobertFlatt what JDK and CC/LLVM do you use? Can you please provide full build log for comparison? What is wrong here??? I am running |
|
I went back to your build and checked the file sizes in the same was as I did for my build (above) Which confirms your diagnosis of the symptoms. But a cause eludes me. Here I use:
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 Attached is the build log from my Ubuntu build. |
|
|
I know those documents and the others. I have tried various combinations starting from the default one. I have tried now Still the same issue :-( Note that I did not change |
|
With the same problem: |
|
I can't replicate this. I get: Thinking of tests for you to try, I looked back and see we have already done what I would suggest. But these were the ones that I built from your project files, Looking at yours I see: Compare with #1585 (comment): We have a build symptom, but not one I can replicate. Since I don't know of any other cases (and this is app install so everybody uses it) I can only conclude it is something about the build environment used. I'm not assigning blame, I'm looking a hint of a cause.
|
I start with the default unmodified buildozer.spec at first, just the application name and bundle change. I know P4A has its own recommendations that will follow when no version request is provided. Changing the
I am configuring them myself. Everything else works fine (even RTOS builds kind of tasks). Nothing unusual. I played with Debian11 VM in order to have clean playground. Now I also have new mac to get XCode and faster builds. No change.
I always do I will try to generate full build logs tomorrow.. and read them line by line ;-) One thing I can confirm is that
So it seems like a build / bundle stage problem. Something is missing. Or error occurs and it is not handled thus skipped step is omitted. Anyways thanks for confirming that things works for you in a default configuration. What GCC / LLVM compiler version do you use exactly? |
Yes, libpybundle.so is 60 bytes when built on your computers (not as far as I know otherwise). As shown by unzipping the apk. No need to install to see the issue, just Please confirm this with Hello World, my data is from the broken compass example. In the project directory what does this return? ( Also But all the real lib*.so are there and apparently the right size.
The LLVM tools in the default NDK (25b) For this process default everything is really important |
|
Here goes the zip with buildozer-kivy-examples-guide-quickstart.zip The unzipped APK content: |
This is the issue as expected. The build log is incomplete, please attach a complete build (only) log And what is the answer to this question?:
|
yup :-(
What do you mean incomplete? This is full build log executed on an empty project with all defaults (provided in zip file): If you mean verbose build ( Please provide a command for "complete build (only)" if its none of the above. Idea: Create
I guess you want to see the files and sizes inside? It seems the python bundle is there built and ready? Any hints welcome :-) |
Yes, that is great, looks like all the files for
Something like this (and more before) is missing from the end of your log. Attached is my HelloWorld log (log.txt), you can see what the "and more" is. After the end of your log, mine copies some files to a directory,the same directory you listed the contents of above. As you can see from my log, I still can't replicate what you see. EDIT: maybe there is a flush() issue with stdout/stderr to the log file that is hiding the error? |
|
Wait there's more... |
Okay, so there is the trouble! The log from my machine is complete! Starting from a clean build (only
That does not happen for me! And this seems to be the problem! We might have a probem cause candidate :-)
Because build process should be the same for all machines and clearly it is not.. question why?
I will also try to redirect stderr to stdout maybe this is the missing part and this is why some parts are not there..? Thank you for the reference! :-)
Okay here are the steps described:
I don't think that location matters, but I will retest in
You have asked to stay all default so I did. Changing the api does not change anything (btw. current API is 34 already).
This is done: Will report back in a moment after build :-) Thanks @RobertFlatt ! :-) |
|
NO WAY!!! IT WORKS NOW!!!!!! o_O I have only changed hello-buildozer-v-android-debug-deploy-run-logcat-stderr_to_stdout-1697531548.zip UPDATE: Default API and API=34 works fine. So the problem is in the build directory???? o_O UPDATE: Android examples from the kivy git master also build and start fine when moved to another location (i.e. Thank you @RobertFlatt !!! =) |
|
👍 |
|
In order to decide if we should close the issue, or start an investigation on it:
|
|
Thanks @misl6 :-) The fix is not here yet so please keep the issue open until it is resolved. Almost certainly there are two possible causes:
If exactly the same project is copied with no git involved to let's say I am trying to pinpoint the problem and create a fix. You are more experienced and familiar with both Buildozer and P4A so if you could drop a hint and/or find a problem your support would be highly appreciated :-) |
|
Okay, so there two more possible causes:
|
|
|
Thanks @RobertFlatt :-) The I am debugging the Buildozer now step by step with |
|
@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 |
|
Okay so the problem seems to be in P4A rather in Buildozer. I have spent some time to track down and get familiar with Buildozer internals.. now its time for P4A. The problem may be at the "Package the application" stage at the end of build. |
|
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have the means to take action. Please reach out if you have or find the answers we need so that we can investigate further. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Versions
Description
_python_bundle does not existerror on application run.private.tarcontains onlyp4a_env_vars.txt.libpybundle.sohas only 60 bytes and does not contain any bundle.kivy-2.1.0/examples/android/compassdirectory with build log, android logcat, and the produced apk.compass.tar.gz
The text was updated successfully, but these errors were encountered: