使用MediaStore与相机Intent的EXTRA_OUTPUT安全存图及异常处理问询

Great question—let’s break down what’s going on here and fix these problems properly. First, your core approach using MediaStore.ACTION_IMAGE_CAPTURE with contentResolver.insert() is not misused—it’s the correct way to handle photo storage under Android’s scoped storage rules. The issues you’re seeing come from edge cases with MediaStore’s database sync and duplicate file names.

Why does contentResolver.insert() return null for the same filename? #

When you manually delete the incomplete photo, the file is gone from storage, but MediaStore’s internal database might not sync that deletion immediately. So when you try to insert a new entry with the same DISPLAY_NAME, MediaStore detects an existing (stale) database entry and rejects the insert, returning null.

Solution 1: Use unique filenames (recommended) #

The simplest way to avoid this conflict entirely is to generate a unique filename every time. Add a timestamp or random string to ensure no duplicates:

val filename = "my_photo_${System.currentTimeMillis()}" // Unique via timestamp
val imageData = ContentValues().apply {
    put(MediaStore.MediaColumns.DISPLAY_NAME, "${filename}.jpg")
    put(MediaStore.MediaColumns.MIME_TYPE, "image/jpeg")
    put(MediaStore.MediaColumns.RELATIVE_PATH, "DCIM/MyPath")
}
val imageUri = contentResolver.insert(MediaStore.Images.Media.EXTERNAL_CONTENT_URI, imageData)

This eliminates the problem at its source and requires no extra cleanup logic.

Solution 2: Query and delete stale entries before insertion #

If you need to use a fixed filename, explicitly check for existing MediaStore entries matching that name and delete them before inserting:

private fun getExistingImageUri(targetFilename: String): Uri? {
    val projection = arrayOf(MediaStore.Images.Media._ID)
    val selection = "${MediaStore.MediaColumns.DISPLAY_NAME} = ?"
    val selectionArgs = arrayOf("${targetFilename}.jpg")

    contentResolver.query(
        MediaStore.Images.Media.EXTERNAL_CONTENT_URI,
        projection,
        selection,
        selectionArgs,
        null
    )?.use { cursor ->
        if (cursor.moveToFirst()) {
            val id = cursor.getLong(cursor.getColumnIndexOrThrow(MediaStore.Images.Media._ID))
            return ContentUris.withAppendedId(MediaStore.Images.Media.EXTERNAL_CONTENT_URI, id)
        }
    }
    return null
}

// Usage before inserting
val targetFilename = "fixed_name_photo"
val staleUri = getExistingImageUri(targetFilename)
staleUri?.let { contentResolver.delete(it, null, null) }

// Now proceed with insert as usual
val imageData = ContentValues().apply {
    put(MediaStore.MediaColumns.DISPLAY_NAME, "${targetFilename}.jpg")
    put(MediaStore.MediaColumns.MIME_TYPE, "image/jpeg")
    put(MediaStore.MediaColumns.RELATIVE_PATH, "DCIM/MyPath")
}
val imageUri = contentResolver.insert(MediaStore.Images.Media.EXTERNAL_CONTENT_URI, imageData)

This cleans up any stale database entries that might block your insert.

Bonus: Improve cancel/switch cleanup #

You mentioned handling the incomplete photo in onActivityResult, but for modern Android, use the Activity Result API (since startActivityForResult is deprecated) for more reliable cleanup:

// Register the launcher in your Activity/Fragment
val takePictureLauncher = registerForActivityResult(ActivityResultContracts.StartActivityForResult()) { result ->
    if (result.resultCode != Activity.RESULT_OK) {
        // Delete the empty file if the user canceled or the camera failed
        imageUri?.let { contentResolver.delete(it, null, null) }
    }
}

// Launch the camera intent
imageUri?.let { uri ->
    val intent = Intent(MediaStore.ACTION_IMAGE_CAPTURE).apply {
        putExtra(MediaStore.EXTRA_OUTPUT, uri)
    }
    intent.resolveActivity(packageManager)?.let {
        takePictureLauncher.launch(intent)
    }
}

This ensures that any empty or incomplete files are removed immediately when the camera flow is canceled.

内容的提问来源于stack exchange，提问作者Austin Chang