[ian-wd]

Problem

MediaStore.copyToMediaStore fails every time on Samsung devices running Android 10 (API 29), including 4.0.1 with #146.

The library inserts a normal row, then flips it to pending with a separate IS_PENDING=1 update. On Samsung's Android 10 MediaProvider that update makes the row inaccessible to its own app:

Unexpected error during copyToMediaStore: Failed to write file: java.io.FileNotFoundException: No item at content://media/external_primary/images/media/23?includePending=1
E DatabaseUtils: java.lang.SecurityException: net.xxx.xxx has no access to content://media/external_primary/images/media/23?includePending=1
E RNFS2   : Failed to cleanup MediaStore entry: ...

#146's setIncludePending doesn't restore access: write, query, update, commit and delete all fail with both the plain and the includePending URI. Stock AOSP Android 10 and Android 11+ work with the old flow, which is why it doesn't reproduce on an emulator.

Solution

On Android 10 only, insert the row with IS_PENDING=1 already in the insert ContentValues, then write, commit (IS_PENDING=0) and clean up through the plain URI. The separate pending update is skipped. #146's setIncludePending wrapping is removed.

Android 11+ keeps the existing sequence, createMediaFile still inserts a non-pending row, and the JS API is unchanged.

Verified (Firebase Test Lab)

Device	4.0.0 / 4.0.1	This PR
Galaxy A10 (SM-A105FN), Android 10	3/3 saves fail	3/3 saves OK, stored file byte-identical
Galaxy S9 (SM-G960F), Android 10	3/3 saves fail	—
AOSP Android 10 emulator	OK	OK
Android 11 / 14 (virtual)	—	OK