Warning on react-native 0.49.x

[macrozone]

I get this warning:

Module RNFetchBlob requires main queue setup since it overrides `constantsToExport` 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.

can be fixed similar to this: https://github.com/wix/react-native-navigation/pull/1983/files

[eugenehp]

same here +1

[jbrodriguez]

You can also check https://github.com/Microsoft/react-native-code-push/pull/1035/files

[dallen4]

@jbrodriguez is there a PR to get this fix merged into the repo?

[klaasman]

PR created, see #674 (repo moved) joltup#10

[isaachinman]

Also seeing this warning.

[wedneyyuri]

Hi Guys, you can ignore this type of warning using the YellowBox module:

import { YellowBox } from 'react-native';

// React native 0.55.4 is currently migrating to a new React API.
// Some warnings are expected in this version.
YellowBox.ignoreWarnings([
    'Warning: isMounted(...) is deprecated',
    'Module RCTImageLoader requires main queue setup',
    'Module RNFetchBlob requires main queue setup',
]);

[IamMasterWayne]

Module RNFetchBlob requires main queue setup since it overrides constantsToExport 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.
this is bothering !

[eseQ]

And? What about fix this issue?

[franjbeltran]

@dictory we already have a fix to this on master: facebook/react-native#17504