3.5.0 (2023-10-19)
Two breaking changes:
- VisionCamera 3.5.0 changes the way Frame Processor Plugins are registered - they now should be registered in the
FrameProcessorPluginRegistry
from within astatic
block on Android, and theVISION_EXPORT_FRAME_PROCESSOR_PLUGIN
macro on iOS. See the docs for more information. (The old way will still work, but the new way is more stable) - VisionCamera 3.5.0 also changes the way Frame Processor Plugins are loaded/initialized. Instead of
VisionCameraProxy.getFrameProcessorPlugin(..)
, you should now useVisionCameraProxy.initFrameProcessorPlugin(..)
. (The old way will still work, but will be removed in the next version)
✨ Features
- Make Frame Processors work on API <29 (#2041) (217461f)
- Reintroduce Macros for Frame Processor Plugin registration (#2027) (a291642)
- Rename
getFrameProcessorPlugin
toinitFrameProcessorPlugin
(#2038) (07027d8)
🐛 Bug Fixes
- Add
getFrameProcessorPlugin
for backwards compatibility (#2040) (da25aa1) - Fix
torch
not working on iOS (#2031) (89dfd35) - Fix build on Xcode 14 (#2033) (2666ac5)
- Initialize Plugins in a
static
block of ReactPackage (#2039) (3929c0a) - Remove unneeded
kotlin-android-extensions
dependency (#2034) (9573ae1)