-
Task
-
Resolution: Unresolved
-
P2: Important
-
None
-
6.10
-
None
There has been multiple accounts of us breaking FFmpeg provisioning for Android on accident, without catching it in CI. See list of related bug reports below.
It should be possible for us to catch this breaking during integration, since we get a very clear runtime crash during startup whenever FFmpeg is not correctly configured.
Points to investigate:
- Can we detect runtime linker crash correctly with auto-tests?
- Run Android auto-tests for ARM64 on macOS using emulator
- Run Android auto-tests for ARM32 on Windows using emulator