Try files read-write in your application designated location in the
first place - that is app.user_data_dir and auto-adjusts location
according to runtime platform for you - this will confirm what you
want to do works but the location is the problem. Each Android is
different (depending on minor, major, api version, vendor, phone
model, etc etc) and they change it constantly so its a moving target
maintenance nightmare, welcome to the real world Neo :-)
https://kivy.org/doc/stable/api-kivy.app.html#kivy.app.App.user_data_dir
Another hint maybe here:
https://stackoverflow.com/questions/42466607/kivy-get-the-path-to-dcim-folder-on-any-android-device
Here is some example with code:
https://karobben.github.io/2021/03/12/Python/kivy-write2android/
I found PUDB debugger extremely helpful in Python development that
provides simple terminal ui (tui) to single step your application,
with insight to variable values, you may even execute commands in REPL
in between the lines of your code. This will make even most surprising
situations clear black on white and save you lots of time :-) I use
desktop PC to develop my application and then just cross compile it to
a mobile, so I debug on a desktop, but it should be possible to debug
directly on the mobile too (adb/ssh?) :-)
Have fun :-)
Tomek
ps/2: If you work on macOS and/or pudb output is messed up on single
stepping use `from os import environ;
environ['KIVY_LOG_MODE'] = 'MIXED'`
--
CeDeROM, SQ7MHZ,
http://www.tomek.cedro.info