[cc'ing the python-for-android project as this affects them too]
I've just done an upgrade of my application and the existing save game
data in /storage/emulated/0/... was lost. AGH.
So, according to
http://developer.android.com/guide/topics/data/data-storage.html we
need to have a better solution for this.
For my application I need to store a smallish amount of data. I
*think* I would actually be able to get away with storing it in the
"Shared Preferences".
I believe that's where the kivy config should be stored by default.
Nothing I've read about the Internal Storage says anything about file
persistence across upgrades. They do explicitly say that files are
removed when the application is removed. I really wish I knew what
Kivy was doing differently that resulted in the files being removed
across upgrades (even reinstalls of the same *version*.)
Regardless, we shouldn't be using the environment variable for that
storage location anyway; we should be exposing the
getFilesDir()/getDir() etc. API in the android module.
Then there's External Storage which is definitely left alone through
application upgrades and removals. Its state and location is obtained
using getExternalStorageState() and getExternalFilesDir().
It'd also be good to expose the API for saving files to be shared:
getExternalStoragePublicDirectory()
I believe it would be valuable and correct to expose this API in
python-for-android and use it in Kivy.
Richard
> --
> You received this message because you are subscribed to the Google Groups
> "Kivy users support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
kivy-users+...@googlegroups.com.
> For more options, visit
https://groups.google.com/groups/opt_out.
>
>