Change Details

Here's how I tested: 1. Open up iOS simulator and Android emulator 2. Send message from iOS to Android. Confirm it renders on both sides, ideally without any transition delay on the sending side between local and remote URIs 3. Same as 3 but from Android to iOS 4. Make sure image copy still works on iOS (we use `SDWebImage` directly in `patches/@react-native-clipboard+clipboard+1.11.1.patch`) I did all of these steps once with dev buils on iOS / Android, and another again with release builds for both.

Here's how I tested: 1. Open up iOS simulator and Android emulator 2. Send message from iOS to Android. Confirm it renders on both sides, ideally without any transition delay on the sending side between local and remote URIs 3. Same as 3 but from Android to iOS 4. Make sure image copy still works on iOS (we use `SDWebImage` directly in `patches/@react-native-clipboard+clipboard+1.11.1.patch`) I did all of these steps once with dev buils on iOS / Android, and another again with release builds for both. Then, separately, I was able to confirm that it could render an SVG data URI on iOS / Android and in dev / release modes using [this patch](https://gist.github.com/Ashoat/b817a9b8fec02537f3f2145594c9721c).

Here's how I tested: 1. Open up iOS simulator and Android emulator 2. Send message from iOS to Android. Confirm it renders on both sides, ideally without any transition delay on the sending side between local and remote URIs 3. Same as 3 but from Android to iOS 4. Make sure image copy still works on iOS (we use `SDWebImage` directly in `patches/@react-native-clipboard+clipboard+1.11.1.patch`) I did all of these steps once with dev buils on iOS / Android, and another again with release builds for both. Then, separately, I was able to confirm that it could render an SVG data URI on iOS / Android and in dev / release modes using [this patch](https://gist.github.com/Ashoat/b817a9b8fec02537f3f2145594c9721c).