Scoped Storage migration for apps targeting API 30

Immediate vs Grace‑Period Migration

On Android 13 the requestLegacyExternalStorage flag is ignored. Any absolute path access that still relies on legacy storage will throw FileNotFoundException or SecurityException. Therefore, if your app reaches Android 13 before you finish refactoring, crashes are inevitable.

Keeping the flag gives you a short window to support Android 10–12 while you work on the migration. However, it keeps technical debt alive and delays necessary refactoring of third‑party libraries that still expect java.io.File objects.

Recommendation: If you are targeting API 30 and expect to ship on Android 13, start refactoring immediately. The grace period offered by the flag is too narrow to cover the time needed to update libraries, rewrite code, and run comprehensive tests.

Practical Migration Steps

1. Audit absolute path usage – run a static analysis or grep for new File(" and filePath patterns.
2. Replace media file access – use MediaStore queries and ContentResolver for reading/writing images, audio, and video. For example:

   Uri uri = MediaStore.Images.Media.getContentUri("external");
   ContentValues values = new ContentValues();
   values.put(MediaStore.Images.Media.DISPLAY_NAME, "photo.jpg");
   values.put(MediaStore.Images.Media.MIME_TYPE, "image/jpeg");
   Uri newUri = getContentResolver().insert(uri, values);
   

3. Expose non‑media files – create a FileProvider in the manifest and use FileProvider.getUriForFile() to obtain a content URI. Ensure the provider’s paths.xml covers the directories you need.
4. Update third‑party libraries – if a library still requires a File, either wrap the library call with a FileProvider URI conversion or replace the library with a media‑aware alternative.
5. Remove legacy flag – delete android:requestLegacyExternalStorage="true" from the application tag in AndroidManifest.xml.

Verification Checklist

• Run the app on an Android 13 device or emulator. Verify that no FileNotFoundException or SecurityException is logged when performing file operations.
• Use a test harness that iterates over all known absolute paths in the app’s codebase and attempts to open them via ContentResolver.openInputStream(Uri). Log any failures.
• Check Logcat for any lingering legacy‑storage warnings or errors such as LegacyExternalStorage deprecation notices.
• Confirm that the manifest no longer contains the legacy flag and that all storage accesses reference content:// URIs.

Missing Diagnostic Detail

To fine‑tune the recommendation, could you provide a list of third‑party libraries your app uses that still expect java.io.File objects? If none remain, the migration can proceed without additional wrappers.