I can't use the library . There is some problem with the RNFSManager.RNFSFileTypeRegular.... I think so....

[s-mohan-prasath]

TypeError: null is not an object (evaluating 'RNFSManager.RNFSFileTypeRegular') at node_modules\react-native\Libraries\Core\ExceptionsManager.js:null in reportException at node_modules\react-native\Libraries\Core\ExceptionsManager.js:null in handleException at node_modules\react-native\Libraries\Core\setUpErrorHandling.js:null in handleError at node_modules\expo\build\errors\ExpoErrorManager.js:null in errorHandler
at node_modules\expo\build\errors\ExpoErrorManager.js:null in
at node_modules\@react-native\polyfills\error-guard.js:null in ErrorUtils.reportFatalError at node_modules\metro-runtime\src\polyfills\require.js:null in guardedLoadModule at http://192.168.163.242:19000/index.bundle?platform=android&dev=true&hot=false&strict=false&minify=false:null in global code

Invariant Violation: Failed to call into JavaScript module method AppRegistry.runApplication(). Module has not been registered as callable. Registered callable JavaScript modules (n = 11): Systrace, JSTimers, HeapCapture, SamplingProfiler, RCTLog, RCTDeviceEventEmitter, RCTNativeAppEventEmitter, GlobalPerformanceLogger, JSDevSupportModule, HMRClient, RCTEventEmitter. A frequent cause of the error is that the application entry file path is incorrect. This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native. at node_modules\react-native\Libraries\Core\ExceptionsManager.js:null in reportException at node_modules\react-native\Libraries\Core\ExceptionsManager.js:null in handleException at node_modules\react-native\Libraries\Core\setUpErrorHandling.js:null in handleError at node_modules\expo\build\errors\ExpoErrorManager.js:null in errorHandler
at node_modules\expo\build\errors\ExpoErrorManager.js:null in
at node_modules\@react-native\polyfills\error-guard.js:null in ErrorUtils.reportFatalError at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:null in __guard at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:null in callFunctionReturnFlushedQueue

Invariant Violation: Failed to call into JavaScript module method AppRegistry.runApplication(). Module has not been registered as callable. Registered callable JavaScript modules (n = 11): Systrace, JSTimers, HeapCapture, SamplingProfiler, RCTLog, RCTDeviceEventEmitter, RCTNativeAppEventEmitter, GlobalPerformanceLogger, JSDevSupportModule, HMRClient, RCTEventEmitter. A frequent cause of the error is that the application entry file path is incorrect. This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native. at node_modules\react-native\Libraries\Core\ExceptionsManager.js:null in reportException at node_modules\react-native\Libraries\Core\ExceptionsManager.js:null in handleException at node_modules\react-native\Libraries\Core\setUpErrorHandling.js:null in handleError at node_modules\expo\build\errors\ExpoErrorManager.js:null in errorHandler
at node_modules\expo\build\errors\ExpoErrorManager.js:null in
at node_modules\@react-native\polyfills\error-guard.js:null in ErrorUtils.reportFatalError at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:null in __guard at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:null in callFunctionReturnFlushedQueue

Invariant Violation: Failed to call into JavaScript module method AppRegistry.unmountApplicationComponentAtRootTag(). Module has not been registered as callable. Registered callable JavaScript modules (n = 11): Systrace, JSTimers, HeapCapture, SamplingProfiler, RCTLog, RCTDeviceEventEmitter, RCTNativeAppEventEmitter, GlobalPerformanceLogger, JSDevaScript modules (n = 11): Systrace, JSTimers, HeapCapture, SamplingProfiler, RCTLog, RCTDeviceEventEmitter, RCTNativeAppEventEmitter, GlobalPerformanceLogger, JSDevSupportModule, HMRClient, RCTEventEmitter. A frequent cause of the error is that the application entry file path is incorrect. This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native. at node_modules\react-native\Libraries\Core\ExceptionsManager.js:null in reportExceptionat node_modules\react-native\Libraries\Core\ExceptionsManager.js:null in handleExceptionat node_modules\react-native\Libraries\Core\setUpErrorHandling.js:null in handleErrorat node_modules\expo\build\errors\ExpoErrorManager.js:null in errorHandlerat node_modules\expo\build\errors\ExpoErrorManager.js:null in at node_modules\@react-native\polyfills\error-guard.js:null in ErrorUtils.reportFatalErrorat node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:null in __guardat node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:null in callFunctionReturnFlushedQueue

[jijisduty]

You are using Expo. react-native-fs is not compatible with Expo. If you are using Expo and need to work with the file system in your app, Expo provides its own file system API that you can use instead.