My app manages a set of data files organized into folders. Of course they are all under the app's root folder of:
getFilesDir().getAbsolutePath() As part of my saving of the application state in onPause, I need to save the current directory. Because of the way I navigate up and down the folder tree, the most convenient form for me to store the current directory is as an absolute path. I could do that, but I have a concern. What if the user upgrades his Android OS after my app has saved the current folder info? Is it possible that some future version of Android will use a different app path for my documents? If so, that would invalidate my saved current directory, and the next time the user tries to open my app after that Android upgrade, it will probably crash with an improperly formed full path name. I don't care what the absolute path is to my app's documents. I just don't want it changing behind my back. Is that something I need to worry about? Or must I find a way to save the relative folder name rather than the absolute? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
