Return the primary external storage directory where this application's OBB files (if there are any) can be found. Note if the application does not have any OBB files, this directory may not exist.

This is like Context.FilesDir in that these files will be deleted when the application is uninstalled, however there are some important differences:

• External files are not always available: they will disappear if the user mounts the external storage on a computer or removes it.
• There is no security enforced with these files. For example, any application holding NoType:android/Manifest$permission;Href=../../../reference/android/Manifest.permission.html#WRITE_EXTERNAL_STORAGE can write to these files.

Starting in NoType:android/os/Build$VERSION_CODES;Href=../../../reference/android/os/Build.VERSION_CODES.html#KITKAT, no permissions are required to read or write to the returned path; it's always accessible to the calling app. This only applies to paths generated for package name of the calling application. To access paths belonging to other packages, NoType:android/Manifest$permission;Href=../../../reference/android/Manifest.permission.html#WRITE_EXTERNAL_STORAGE and/or NoType:android/Manifest$permission;Href=../../../reference/android/Manifest.permission.html#READ_EXTERNAL_STORAGE are required.

On devices with multiple users (as described by Android.OS.UserManager), multiple users may share the same OBB storage location. Applications should ensure that multiple instances running under different users don't interfere with each other.

[Android Documentation]