Warning: Module FFmpegKitReactNativeModule requires main queue setup since it overrides init but doesn't implement requiresMainQueueSetup.

[manuelbieh]

Description
Hey. I just installed and set up ffmpeg-kit for my brand new React Native app and once I start the app I get a warning:

Module FFmpegKitReactNativeModule requires main queue setup since it overrides `init` but doesn't 
implement `requiresMainQueueSetup`. In a future release React Native will default to initializing all 
native modules on a background thread unless explicitly opted-out of

Expected behavior
There should be no warning

Current behavior
There is a warning

To Reproduce

npx react-native init TestApp
yarn add ffmpeg-kit-react-native

set platform :ios, '12.1' in ios/Podfile

npx pod-install

add import { FFmpegKit, ReturnCode } from 'ffmpeg-kit-react-native'; to any file (e.g. App.js)
build and run the app

Screenshots

Logs

BUNDLE  ./index.js 

WARN  Module FFmpegKitReactNativeModule requires main queue setup since it overrides `init` but doesn't 
implement `requiresMainQueueSetup`. In a future release React Native will default to initializing all 
native modules on a background thread unless explicitly opted-out of.

Environment

• Platform: iOS
• Architecture: arm64 m1 macbook air
• Version 4.5
• Source branch (if applicable) v4.5 release from npm
• React Native 0.65.1
• Xcode version (if applicable) 15
• Cocoapods version (if applicable) 1.11.2

Other
Via Google I found other libs with the same bug (and also a possible 4 lines fix, see: facebook/react-native#24314)

[tanersener]

I don't know why but we don't have this issue in our test apps under the ffmpeg-kit-test repo.

Anyway, I'll mark this as enhancement and address before the next release.

[manuelbieh]

I will try to remove all the project relevant stuff from my repo and create a new repo where the error can (hopefully) be reproduced tomorrow.

[tanersener]

You don't need to. I've already seen it in a new project and fixed it on the development-react-native branch.

I just don't know why we haven't seen it on our apps. It seems like it is not a new warning/check coming with the latest react-native versions; it was already there for a few years.

[tanersener]

Fixed in v4.5.1 release.