Change Details

Initially just confirmed I could build and bundle the app on iOS and Android. Working on testing the actual functionality, but I want to see if CI passes first

* Confirmed I could build and bundle the app on iOS and Android * On release builds of both iOS and Android, tested the four usages of ffmpeg in our codebase, all called from `native/media/ffmpeg.js`: * `getVideoInfo` * `transcodeVideo` * `generateThumbnail` * `hasMultipleFrames`, which actually isn't in active use in our codebase. To test it I had to use [this patch](https://gist.github.com/Ashoat/3e8f98d7b82a91b5467ef2861d4a506e) to make it so we transcode GIFs if they have multiple frames. It correctly ascertained whether the GIFs had multiple frames on both iOS and Android, but transcoding failed afterwards, so I left this functionality disabled. Working on testing the actual functionality, but I want to see if CI passes first

Initially just c* Confirmed I could build and bundle the app on iOS and Android. * On release builds of both iOS and Android, tested the four usages of ffmpeg in our codebase, all called from `native/media/ffmpeg.js`: * `getVideoInfo` * `transcodeVideo` * `generateThumbnail` * `hasMultipleFrames`, which actually isn't in active use in our codebase. To test it I had to use [this patch](https://gist.github.com/Ashoat/3e8f98d7b82a91b5467ef2861d4a506e) to make it so we transcode GIFs if they have multiple frames. It correctly ascertained whether the GIFs had multiple frames on both iOS and Android, but transcoding failed afterwards, so I left this functionality disabled. Working on testing the actual functionality, but I want to see if CI passes first