3

As far as I've noticed, using getFilesDir() to store data (camera captures in my case) is somewhat temporary. I say somewhat because if I close and reopen the app, I'm able to access the directory and files list, but not the file itself.

Is my logic wrong or is that by design? Out of the 2 methods, which is more recommended in :

  1. general
  2. my case (privacy is needed)
Kasım Özdemir
  • 5,414
  • 3
  • 18
  • 35
sonofel
  • 112
  • 3
  • 8
  • [this link](https://developer.android.com/training/data-storage) say getFileDir is app specific and no other app cant read files in this dir. but when use getExternalFileDir all apps can read files in this dir – Mehdi Yari Apr 29 '20 at 19:55
  • "using getFilesDir() to store data (camera captures in my case) is somewhat temporary" -- it is not temporary. "I say somewhat because if I close and reopen the app, I'm able to access the directory and files list, but not the file itself" -- please provide a [mcve] showing your code that implements the "access the directory and files list, but not the file itself" logic. "Out of the 2 methods, which is more recommended in" -- `getFilesDir()`, unless the user needs independent access to the content. – CommonsWare Apr 29 '20 at 19:58

3 Answers3

6

Simply, getFilesDir() refers to internal storage that cannot be accessible outside your application. It's not explorable by the device as well.

getExternalFilesDir() refers to external storage, it's a type of App-specific storage. this can be explorable as you find its directory in

data/data/your package name

In general, you may use external storage as internal storage may be limited.

For privacy, if you need you to file security, use getFilesDir() as it's not accessible outside your application as I mentioned before.

MustafaKhaled
  • 1,343
  • 9
  • 25
2

Update for the latest Android (currently Android 13)

In the old days getFilesDir() used to mean internal storage, and getExternalFilesDir() used to mean anything plugged in (usually an SD card).

These days phones don't have SD card slots, so the device emulates external storage by grabbing a slice of internal storage for the purpose. So the historic differences - that internal was faster and smaller, and external slower and larger - are generally no longer true.

In both cases apps get scoped storage - i.e. a directory they can access without permissions, which isn't accessible by any other app (though see below). This has been the case since Android 10 (but only enforced in Android 11).

Files stored under getFilesDir() and getExternalFilesDir() will be deleted when the app is uninstalled, but will persist until then. (If you're finding a file disappears before then, you have a different problem. I would suggest posting your code in a separate question).

The only major remaining difference between internal and external is that apps can get request a permission to read/write the entirety of external storage, including files it doesn't own. So don't use external for files that need to remain private to the app.

More information in this article: https://medium.com/@tdcolvin/demystifying-internal-vs-external-storage-in-modern-android-c9c31cb8eeec

HughHughTeotl
  • 5,439
  • 3
  • 34
  • 49
1

The main difference between the two is: getFilesDir() - This path will be hidden from the user. This is more secure approach. getExternalFilesDir() - Accessible by the user.

Received a good documentation on this which provides clear understanding: http://androidvogella.blogspot.com/2015/12/getfilesdir-vs-getexternalfilesdir-vs.html

atla praveen
  • 49
  • 1
  • 4