No module name PIL

[Thasatsaya Sriwongchai]

I try to deploy my python app (https://github.com/thasatsaya/myproject) using kivy , kivymd , buildozer & android debug bridge followed by these instructions (https://youtu.be/pzsvN3fuBA0) in which I also use ubuntu on windows. Furthermore after I can deploy his app I have add the requirements in buildozer.spec file which is  " requirements = kivy==2.0.0, kivymd==0.104.1, sdl2_ttf == 2.0.15, pillow " and install kivymd using " pip install kivymd==0.104.1" as followed by the Kivymd Github Page (https://github.com/kivymd/KivyMD) and I also try code from this channel (https://youtu.be/VsTaM057rdc) and it also work fine. but for my code after running command  adb -s DEVICE_ID logcat *:S python:D after install app on my phone by usb it show " No module name PIL" in which most forum said by adding pillow to the requirements it should be fixed but I have already add that and it still show this error.

  

[Robert]

What version of Buildozer are you using?

Was the p4a version changed from the default ?

Do any of these apply? https://github.com/Android-for-Python/Android-for-Python-Users#non-deterministic-behavior

Please post the full build log as a .txt  (do a buildozer appclean first so everything is rebuilt)

[Thasatsaya Sriwongchai]

- Buildozer 1.4.0.dev0

- I'm not sure about p4a version but the thing I change related to p4a is p4a.branch = develop & p4a.fork = thasatsaya which is my github ( I got this way of setup fork from  https://youtu.be/VsTaM057rdc)

- I have run using buildozer android debug so from my understanding it didn't run as root (cause no sudo thing) for no.2 I use ubuntu on window but didn't do any disk mount so I think it's completely separated but no3 I have no idea what that mean sorry. 

I have rebuild by using buildozer android clean follow by buildozer android debug and add crash.txt according to your suggest.

ในวันที่ วันศุกร์ที่ 1 กรกฎาคม ค.ศ. 2022 เวลา 23 นาฬิกา 44 นาที 00 วินาที UTC+7 Robert เขียนว่า:

[Robert]

Never rely on what some dweeb on Youtube says.
Youtube imparts confidence not competence.

If you want to show you did your due diligence, then reference the documentation.

The first issue is that clever adb trick is wrong. It is missing -r , see adb --help

https://github.com/Android-for-Python/Android-for-Python-Users#appendix-a--using-adb

I don't know if it works otherwise, the simple way to be certain is to copy the .apk and   adb install -r foo.apk

If there is still an issue , try with the release Buildozer (1.3.0) ,  p4a.branch = master (the default) , and no p4a.fork. (the default)
`buildozer appclean`  before the build

If there is still an issue, post the BUILD log

[Thasatsaya Sriwongchai]

As you suggested I edit buildozer.spec file to

- p4a.branch = master instead of develop

- put comment on p4a.fork

- change buildozer to 1.3.0 by using pip install buildozer==1.3.0

then rebuild by using buildozer android clean & buildozer android debug
and install apk file using adb -s DEVICEID install -r APPNAME.apk

I think build log look the same

[Robert]

You are still using the incorrect adb command

If you still have a problem post the BUILD log

[Thasatsaya Sriwongchai]

so what you mean is instead of  adb -s DEVICEID install -r APPNAME.apk replace with adb install -r APPNAME.apk right?

I've try that and build log is still the same.

ในวันที่ วันอาทิตย์ที่ 3 กรกฎาคม ค.ศ. 2022 เวลา 0 นาฬิกา 13 นาที 51 วินาที UTC+7 Robert เขียนว่า:

[Robert]

> adb install -r myapp-0.1-arm64-v8a_armeabi-v7a-debug.apk 

That is one issue fixed (assuming it is the right version of the ,apk file)

Re-check that you are using the master version of p4a (this is important)

Post the apk BUILD log not the apk RUN log.

Do a 'buildozer appclean' before doing the build.

[Thasatsaya Sriwongchai]

I've recheck yes it's on p4a master. And now I add you the build log that I've build after doing buildozer appclean. It's exceed max quota of ubuntu lines so it's missing by some lines.

ในวันที่ วันจันทร์ที่ 4 กรกฎาคม ค.ศ. 2022 เวลา 23 นาฬิกา 44 นาที 26 วินาที UTC+7 Robert เขียนว่า:

[Robert]

Thanks, yes there is a big chunk of the build log missing, but that is OK.

I can see that p4a is not building Pillow.

I saw another user last week, who had followed the same YouTube example as you, and had the same two issues.

In that case after fixing the install issue,  I replicated the issue, and the user confirmed, we fixed the second issue

with p4a.branch=master  this is the default.

(nobody should use the in development version, but it seems that YouTube video misleads)

I demonstrated the fix using the release Buildozer. Perhaps there is an interaction?

So try: uninstall the development version of Buildozer and install the release version

https://github.com/kivy/buildozer/blob/master/docs/source/installation.rst

And please double check that the installed apk is really your latest build.

[Thasatsaya Sriwongchai]

I've deleted buildozer 1.4.0.dev0 and install buildozer 1.3.0 (reinstall-buildozer.txt)
and rebuild the file using ' buildozer appclean ' & ' buildozer android debug ' (build2.txt)

finally I use the adb install -r myapp-0.1-arm64-v8a_armeabi-v7a-debug.apk and I'm sure that it's the right one as the name from build log when they said successfully install is also this one. (crash4.txt)

ในวันที่ วันอังคารที่ 5 กรกฎาคม ค.ศ. 2022 เวลา 13 นาฬิกา 17 นาที 50 วินาที UTC+7 Robert เขียนว่า:

[Robert]

A couple of back to basic things:

If you change buildozer.spec, do you do this?

https://github.com/Android-for-Python/Android-for-Python-Users#changing-buildozerspec

Do any of these apply?

https://github.com/Android-for-Python/Android-for-Python-Users#non-deterministic-behavior

[Thasatsaya Sriwongchai]

- yes I do after I change buildozer.spec

Do any of these apply ?

No 1. I've check through ls -la . All files and folders are not under root (myproject.txt)

No 2. I did not use any mount command so I think my ubuntu on windows is separate from my windows system.

No 3. I have no idea how to check this one

ในวันที่ วันอังคารที่ 5 กรกฎาคม ค.ศ. 2022 เวลา 23 นาฬิกา 57 นาที 29 วินาที UTC+7 Robert เขียนว่า:

[Robert]

'run as root' means logged in as root   (the admin account) , or using sudo.

In the context of a Linux file system, by definition, everything is under root, but that is something different from the root account.

What you checked was 'owned by root', which not 'run as root'.

I suggest some basic Linux tutorial - but not one on YouTube!

[Thasatsaya Sriwongchai]

I've once use sudo while build the app but I've change it from root to 'che' which is ubuntu name already (sudo chown -R che:che). Do you have some other suggestion? 

ในวันที่ วันพุธที่ 6 กรกฎาคม ค.ศ. 2022 เวลา 14 นาฬิกา 01 นาที 32 วินาที UTC+7 Robert เขียนว่า:

[Robert]

I suspect some state somewhere is incorrect, because of that 'sudo buildozer ...`

Changing the ownership of the project files is a good first step.

But for the build databases the state may be wrong, delete and let them self rebuild.

 

Delete both <project>/.buildozer and ~/.buildozer   , use sudo for this.

If you still have an issue delete ~/.gradle (if it exists) and the next one would be ~/.cache , again use sudo.

[Thasatsaya Sriwongchai]

I've try to delete with 'sudo rm -rf /.buildozer' and 'sudo rm -rf  ~/.buildozer' and rebuild with buildozer android debug. The result is failed so I sent you the build log.

ในวันที่ วันพฤหัสบดีที่ 7 กรกฎาคม ค.ศ. 2022 เวลา 0 นาฬิกา 18 นาที 58 วินาที UTC+7 Robert เขียนว่า:

[Robert]

> [ERROR]: Build failed: Requested API target 27 is not available, install it with the SDK android tool.

https://github.com/Android-for-Python/Android-for-Python-Users#androidapi

[Thasatsaya Sriwongchai]

I've try uncomment lines in buildozer.spec and change it to  android.api = 33 as you suggested. The build is successful. But run log is the same. Should I change anything else on buildozer.spec?

ในวันที่ วันพฤหัสบดีที่ 7 กรกฎาคม ค.ศ. 2022 เวลา 23 นาฬิกา 38 นาที 09 วินาที UTC+7 Robert เขียนว่า:

[Robert]

Looking back at the previous post,

In the project directory:

It is not       sudo rm -rf /.buildozer

It is       sudo rm -rf ./.buildozer     (or more simply  sudo rm -rf .buildozer)

At this point I'm starting to run out of ideas.