MediaLibrary.createAssetAsync - Created asset is completely different from original file

🐛 Bug Report

Environment

iOS (Not tested on Android)

Steps to Reproduce

• Create a new asset from an existing file:
  • MediaLibrary.createAssetAsync(uri);
• Get asset info of newly created asset:
  • MediaLibrary.getAssetInfoAsync(asset);
  • FileSystem.getInfoAsync(asset.uri, { md5: true });
• Compare against original file info: FileSystem.getInfoAsync(uri, {md5: true });

Expected Behavior

Original file is copied over as an asset, unmodified or at least has a way to determine if a file has already been turned into an asset.

Actual Behavior

Newly created asset is completely different than original file. MD5 hash, filename, and size no longer match as the file has been opaquely transformed for some reason. There’s no way to compare if the original file actually exists as an asset because no asset properties match the original file properties.

It should also not create duplicate files. Currently you can pass the same uri into createAssetAsync and it will create a duplicate asset with a new filename.

Reproducible Demo

Check the console output: https://snack.expo.io/@justindmyers/bold-beef-jerky

[tsapeta]

Could you try to use asset.localUri instead of asset.uri in FileSystem.getInfoAsync?

It should also not create duplicate files. Currently you can pass the same uri into createAssetAsync and it will create a duplicate asset with a new filename.

I don’t have good news – this is expected behavior. On iOS you can download an image from the internet, save it to photo library multiple times and you’ll get them duplicated. That’s how it works under the hood in the operating system and there is nothing we can do as far as I know.

[github-actions[bot]]

This issue was closed because it has been inactive for 7 days since being marked as stale. Please open a new issue if you believe you are encountering a related problem.