Yeah that definition is perfect, having a little trouble implementing
it though.
I'm just trying to use:
File file = getFilesDir();
this points to:
/data/data/com.foo.bar/files
which is empty though, nothing gets written there during my app's
lifetime. My app's directory structure looks like this:
com/foo.bar
/cache
/databases
webviewstuff.db
/files
/lib
/shared_prefs
com.foo.bar_preferences.xml
should I be seeing databases/preferences? Or am I supposed to be
looking for the existence of /shared_prefs/
com.foo.bar_preferences.xml. If so, is there a proper way to resolve
that path other than kind of hard-coding it into my app?
Thank you
On Mar 18, 11:50 am, Mark Murphy <[email protected]> wrote:
> Mark Wyszomierski wrote:
> >>> Otherwise, checking for files/databases/preferences is pretty typical
> >>> AFAIK.
>
> > This sounds like my best bet - so you're saying at app startup, I can
> > check if files/databases/preferences exists - if it does, this is not
> > my first run, if it is missing, then it's my first run?
>
> For a sufficiently-generous definition of "first run", yes.
>
> You will not be able to distinguish between install and
> install-uninstall-reinstall this way. Hopefully, that distinction does
> not matter.
>
> --
> Mark Murphy (a Commons
> Guy)http://commonsware.com|http://twitter.com/commonsguy
>
> Android App Developer Training:http://commonsware.com/training
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
To unsubscribe from this group, send email to
android-developers+unsubscribegooglegroups.com or reply to this email with the
words "REMOVE ME" as the subject.
