I'm trying to implement deep linking in React Native folowing this doc: https://reactnavigation.org/docs/configuring-links.

The main problem here is that i'm not able to open a specific screen, it always open the main screen.

I'm currently only testing in iOS, but in Android same occurs.

I defined custom url scheme

<dict><key>CFBundleURLName</key><string>com.react_native_starter_kit</string><key>CFBundleURLSchemes</key><array><string>test</string></array></dict>

Defined linking obj

const linking = {  prefixes: ['test://'],  config: {    screens: {      App: {        screens: {          Settings: 'settings/:id',        },      },    },  },};

And Navigation

export const Router = () => {  ...  return (<NavigationContainer linking={linking}><Main /></NavigationContainer>  );};const Main = (props) => {  ...  return (<Stack.Navigator      screenOptions={{ headerShown: false }}      initialRouteName={routesName.App}>      {userToken ? (<Stack.Screen name={routesName.App} component={TabNavigator} />      ) : (<Stack.Screen name={routesName.Auth} component={AuthStack} />      )}</Stack.Navigator>  );};const TabNavigator = () => {  ...  return (<Tab.Navigator><Tab.Screen        name={routesName.Home}        component={HomeStack}        options={navigationOptions(routesName.Home, theme)}      /><Tab.Screen        name={routesName.Settings}        component={SettingsStack}        options={navigationOptions(routesName.Settings, theme)}      /></Tab.Navigator>  );};

When i type test://settings/123, inside safari, or xcrun simctl openurl booted test://settings/123 it should open settings tab, but it always only open main screen. I've tryied a lot of linkin obj combinations, same result always. Even when i remove linking={linking} the behavior is the same, app opens main screen. It is like navigation is ignoring linking={linking}.

I really want to make use of the pencil kit in my react-native application. I just want to know whether I can do it. If yes, then how?

I have found that Show Inspector does something similar on the simulator but right now it looks very ugly at the top of the simulator's screen. It also does not highlight padding, margin and other elements as you hover over the box. Is there anything similar to the image below for React Native ios simulator?

In my react-native-app with expo am trying to implement expo-in-app-purchases("https://docs.expo.io/versions/latest/sdk/in-app-purchases/").I did all setup mentioned in the document.next am trying to build the solution with Xcode and my device.The build always failed with this message:

 node_modules/@hapi/hoek/lib/assert.js:20 throw new AssertError(args);^Error: Method no longer accepts array arguments: tryat new module.exports (/Users/Projects/test/node_modules/@hapi/hoek/lib/error.js:23:19)at module.exports (/Users/Projects/test/node_modules/@hapi/hoek/lib/assert.js:20:11)at Object.exports.verifyFlat (/Users/Projects/test/node_modules/@hapi/joi/lib/common.js:211:9)at internals.Base.method [as try] (/Users/Projects/test/node_modules/@hapi/joi/lib/types/alternatives.js:168:24)at Object.<anonymous> (/Users/Projects/test/node_modules/react- native/node_modules/@react-native-community/cli/build/tools/config/schema.js:35:36)at Module._compile (internal/modules/cjs/loader.js:1137:30)at Object.Module._extensions..js (internal/modules/cjs/loader.js:1157:10)at Module.load (internal/modules/cjs/loader.js:985:32)at Function.Module._load (internal/modules/cjs/loader.js:878:14)at Module.require (internal/modules/cjs/loader.js:1025:19)error Command failed with exit code 1.

am using ios device version 10.3.3(it's ipad).am also trying to configure my sandbox account in this device,but there is no option to set sandbox account.in settings->iTunes&Appstore it only showing automatic downloads nothing else.Like this:

My sandbox Account:

What should i do?

UPDATE:In my iOs phone(14.2) also unable to view the sandbox account why?any help?

SafeAreView is working well in Portrait mode, But doesn't show any effect in Landscape mode

This react-native doc gave fix tot his issue. But it didn't work for me.

Can some one help me to fix this issue?

First of all, just to clarify...

I have done quite some searchings and readings on the existing sources (medium, stackoverflow, apple developer forum, etc.) before asking this "duplicate question" for confirming and concluding my knowledge is correct.

1. Will iOS launch my app into the background if it was force-quit by the user?
2. How to get the push notification payload when force-quit / swipe up to kill the iOS app without tapping on the banner/alert?
3. https://medium.com/fenrir-inc/handling-ios-push-notifications-the-not-so-apparent-side-420891ddf10b
4. Handling Push Notifications when App is Terminated
5. https://developer.apple.com/forums/thread/62005#:~:text=In%20most%20cases%2C%20the%20system,force%20quit%20by%20the%20user.

Before we begin, just to put the terms in very precise manner. Here's what I'm referring when I mention

1. Foreground - App is Active and running, user is basically interacting with the application
2. Background - User tapped on home button after interacting. App remains in background, user can double tap on home button and find the app from App Switcher.
3. Quit - App is actually in background, but it was terminated by the System itself.
4. Kill - App is no longer in background, user double tap on home button and SWIPE the app away from App Switcher.

Use case i'm trying to tackle

App receive push notification in BACKGROUND, QUIT & KILL states then perform certain background actions (updating Application Badge + storing the Notification in device)

1. For background - Yes I've managed to achieve this by having content-available = 1 sent together in APNS payload. Notification banner appear, background action executed!
2. For QUIT - Yes I've managed to achieve this by having content-available = 1 sent together in APNS payload. Notification banner appear, background action executed!
3. For KILL - Notification banner appear, BUT background action is not trigger.

My questions

1. Whenever app is kill, it's not possible to awake the app to perform any background action when notification is receive?
2. How does it works for messaging app like Whatsapp?
3. How should I handle my cases when app is force quit?

• ONLY if user tapped notification banner, my app gets to run those background actions (Increase badge count + storing the data).

• Otherwise, if user choose to tap on App Icon to open my app. The pushed notification won't exist in my app at all, including badge count is not increase.

Below are what I've tested with Whatsapp

Background State

1. Open Whatsapp, tap Home button (keep app in background)
2. Send a text message in device, banner notification appear
3. Open app by tapping app icon, message is there in app.

FORCE QUIT State

1. Open Whatsapp, double tap Home button, swipe app away
2. Send a text message in device, banner notification appear.
3. Open app by tapping app icon, message is there in app.

FORCE QUIT State + WiFi & Cellular data turned OFF

1. Open Whatsapp, double tap Home button, swipe app away
2. Send a text message in device, banner notification appear
3. Turn off WiFi & Cellular data is off. (Confirm and tried to access website via Safari)
4. Open app by tapping app icon, message is there in app.

The tests with Whatsapp, basically concludes that it's possible to have your app awake to perform background actions (Especially with the case of FORCE QUIT State + WiFi & Cellular data turned OFF)

The only "explanation" I'm able to explain myself is, they are using PushKit notifications Framework instead of User Notification Framework.

Update 3 Nov - iOS 13 wakes app even in KILL state

Apparently on iOS 13, like what @hubsi has mentioned down at the comment as well as some comments from Apple forum. iOS 13 does wakes my app even the app was manually killed by the user.

My goal is to detect changes in a user's gallery and implement some actions while the app runs in the background (without the app being active at all).For now, the code below was implemented but the actions I want to perform are only available to execute while the app is active.

import UIKitimport Photosclass ViewController: UIViewController {    var backgroundTask: UIBackgroundTaskIdentifier = .invalid    override func viewDidLoad() {        super.viewDidLoad()        PHPhotoLibrary.shared().register(self)    }}extension ViewController: PHPhotoLibraryChangeObserver {    func photoLibraryDidChange(_ changeInstance: PHChange) {      debugPrint("gallery changed")    }}

SafeAreaView is working well in Portrait mode, But doesn't show any effect in Landscape mode

This react-native doc gave fix to this issue. But it didn't work for me.

Can some one help me to fix this issue?

I know we can load the local image with:

<Image source={require('folder/image.png')}/>

But i need to load the image like this:

<Image source={{uri: 'folder/image.png'}}/>

It works for network images but it doesn't work for local images and even it does not give any error for local images and silently does not display the image. Can anyone tell how to load the local image using the uri property?

I am working on a scenario where I will have to pause here maps navigation (iOS SDK) for some time it not pause. i am use setpause method for that

zIndex has been introduced recently to React-Native to change the position of a View in the stack of layers.

Although, I'm not able to bring a View on top of a Modal component.

My code looks like this:

render() {  return (<View><Modal visible>        {props.children}</Modal><View style={{ zIndex: 1000 }}><Text>Loading...</Text></View></View>  );}

I guess I could stop using <Modal> and create a regular animated <View> that would behave like the Modal, but I'd rather find another solution.

Any idea?

I got the error when run the project.Please help me resolve it. Thank you so much.

Info:

enter image description here

Error:

Error: info Found Xcode workspace "StillError.xcworkspace" infoBuilding (using "xcodebuild -workspace StillError.xcworkspace-configuration Debug -scheme StillError -destination id=26886618-C6CF-463F-9A5F-A23B77E20B00") error Failed to build iOSproject. We ran "xcodebuild" command but it exited with error code 65.To debug build logs further, consider building your app withXcode.app, by opening StillError.xcworkspace. note: Using new buildsystem note: Planning build note: Using build description from diskwarning: Mapping architecture arm64 to x86_64. Ensure that thistarget's Architectures and Valid Architectures build settings areconfigured correctly for the iOS Simulator platform. (in target'OpenSSL-Universal' from project 'Podenter code heres') PhaseScriptExecution [CP]
Copy\ XCFrameworks......

** BUILD FAILED **

The following build commands failed: PhaseScriptExecution [CP]\ Copy
XCFrameworks/Users/_tupt/Library/Developer/Xcode/DerivedData/StillError-bxukiiaafgsohdhalcesljnliurj/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/OpenSSL-Universal.build/Script-329FE3CB18B30DBF34BE47031BE8F397.sh(1 failure)

info Run CLI with --verbose flag for more details.

I'm not able to build a React Native project, which built correctly using Xcode 11, using Xcode 12.5.

I can no longer use Xcode 11 because only more current versions of Xcode carry the necessary API to publish/upload to TestFlight and the app store.

Now I get three build errors:

Cannot initialize a parameter of type 'NSArray<id<RCTBridgeModule>> *' with an rvalue of type 'NSArray<Class> *'Cannot initialize a parameter of type 'NSArray<id<RCTBridgeModule>> *' with an rvalue of type 'NSArray<Class> *'Cannot initialize a parameter of type 'NSArray<id<RCTBridgeModule>> *' with an rvalue of type 'NSArray<Class> *'

I also noticed that deployment targets were automatically upgraded from 10 and 9:

- IPHONEOS_DEPLOYMENT_TARGET = 9.0;+ IPHONEOS_DEPLOYMENT_TARGET = 12.1;

Some new properties were added related to Clang:

+ CLANG_ANALYZER_LOCALIZABILITY_NONLOCALIZED = YES;

How can I configure the project to deploy this app using Xcode 12.5?

$ react-native infoinfo Fetching system and libraries information...System:OS: macOS 11.3CPU: (4) x64 Intel(R) Core(TM) i3-8100B CPU @ 3.60GHzMemory: 256.45 MB / 8.00 GBShell: 3.2.57 - /bin/bashBinaries:Node: 10.16.0 - /usr/local/bin/nodeYarn: 1.21.1 - ~/npm-global/bin/yarnnpm: 6.9.0 - /usr/local/bin/npmWatchman: 4.9.0 - /usr/local/bin/watchmanSDKs:iOS SDK:Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4IDEs:Xcode: 12.5/12E262 - /usr/bin/xcodebuildnpmPackages:react: ^16.11.0 => 16.12.0react-native: 0.61.4 => 0.61.4npmGlobalPackages:react-native-cli: 2.0.1

I'm doing a React native project with notification, using APNs Authentication Key. It works perfectly fine on android and iOS dev.

But when I export ipa as adHoc run on device, the app stop receiving notification when I send noti to a single device using FCM. It only works if I send to all iOS devices.

I am developing app using react native and expo & I have to implement push notifications in app. So far sending and receiving the notifications has no issues but my problems are mainly related to UI design on push notification panel :

Following is my simple notification message configuration :

scheduleNotificationAsync({content: {title: “You’ve got mail! :mailbox_with_mail:”,body: ‘Here is the notification body’,data: { data: ‘goes here’ },},})

Is there any way to design multi line notification?I can use title, subtitle (which only works in iOS) but I want multiple lines in body part. I tried using \n in my body text but it doesn’t work.How to navigate to specific screen in app when button is pressed in notification?I have setup sample category as below :

Notifications.setNotificationCategoryAsync(“daily_question”, [{actionId: “yes”,buttonTitle: “Yes”,},{actionId: “no”,buttonTitle: “No”,},]);

I would like to navigate to specific screen upon pressing of “Yes/No” button but I’m not able to figure out/able to find out, how I can write any action code in configuration.

Is there any way I can design the notification panel content UI part as html/jsx code to have better control over how UI will look like?

Is there any way to add image/table kind of components in notification ui?

It seems like adding image to push notification is under consideration.Any pointers/guidance on achieving above points using expo notification?

If expo notification, cannot achieve above functionalities then what are my options?

Thanks

I don't know why but the tabnavigator and app drawer navigator are not working and I cannot find what the provblem is

AppDrawerNavigator.js for Drawer Navigation, I have doubt with HomeScreen in this code

import * as React from 'react';import { createDrawerNavigator } from 'react-navigation-drawer';import CustomSideBarMenu from './CustomSideBarMenu';import { TabNavigator } from './TabNavigator';import SettingsScreen from '../screens/SettingsScreen';import ContactScreen from '../screens/ContactScreen';import HomeScreen from '../screens/HomeScreen';export const AppDrawerNavigator = createDrawerNavigator({  Home: {    screen: TabNavigator  },  ContactUs: {    screen: ContactScreen  },  Settings: {    screen: SettingsScreen  },},  {    contentComponent: CustomSideBarMenu  },  {    initialRouteName: 'Home'  },)

AppStackNavigator.js for Stack Navigation, I created it for stack navigation and I don;t have a doubt on this component

import * as React from 'react';import { createStackNavigator } from 'react-navigation-stack';import HomeScreen from '../screens/HomeScreen';import DonateScreen from '../screens/DonateScreen';import ChatScreen from '../screens/ChatScreen';import CleaningScreen from '../screens/CleaningScreen';export const AppStackNavigator = createStackNavigator({  Home: {screen: HomeScreen, navigationOptions: { headerShown: false }},  DonateScreen: {screen: DonateScreen, navigationOptions: { headerShown: false }},  ChatScreen: {screen: ChatScreen, navigationOptions: { headerShown: false }},  CleaningScreen: {screen: CleaningScreen, navigationOptions: { headerShown: false }},},{  initialRouteName: 'Home'})

CustomSideBarMenu.js for my custom drawer navigator

import * as React from 'react';import { View, Text, TouchableOpacity } from 'react-native';import { DrawerItems } from 'react-navigation-drawer';import firebase from 'firebase';import { Icon } from 'react-icons';import db from '../config';export default class CustomSideBarMenu extends React.Component {  render() {    return(<View style = {{ flex: 1 }}><DrawerItems {...this.props}/><View style = {{ flex: 1, justifyContent: 'flex-end', paddingBottom: 30, }}><TouchableOpacity style = {{ justifyContent: 'center', padding: 10, height: 30, width: '100%' }}          onPress = {()=> {            this.props.navigation.navigate('LoginScreen')            firebase.auth.signOut()          }}><Icon                name='fontawesome|poweroff'                size={25}                color='#042'                style={{width: 10,  height: 10,}}/><Text>Logout</Text></TouchableOpacity></View></View>    );  }}

TabNavigator.js for tab navigation

import * as React from 'react';import { View, Image } from 'react-native';import { Icon } from 'react-icons';import { createBottomTabNavigator } from 'react-navigation-tabs';import HomeScreen from '../screens/HomeScreen';import DonateScreen from '../screens/DonateScreen';import ChatScreen from '../screens/ChatScreen';import { AppStackNavigator } from '../components/AppStackNavigator';export const TabNavigator = createBottomTabNavigator(  {    Home: {      screen: AppStackNavigator,      navigationOptions: {        tabBarIcon: (<Icon            name="fontawesome|home"            size={25}            color="#042"            style={{ width: 10, height: 10 }}          />        ),        tabBarLabel: 'Home',      },    },    Chat: {      screen: ChatScreen,      navigationOptions: {        tabBarIcon: (<Image            source={require('../assets/chat.png')}            style={{ width: 10, height: 10 }}          />        ),        tabBarLabel: 'Chat',      },    },    Donate: {      screen: DonateScreen,      navigationOptions: {        tabBarIcon: (<Image              source={require('../assets/donate.png')}              style={{ width: 10, height: 10 }}          />        ),        tabBarLabel: 'Donate',      },    },  },  {    defaultNavigationOptions: ({ navigation }) => ({      tabBarIcon: () => {        const routeName = navigation.state.routeName;        if (routeName === 'Home') {          return (<Icon              name="fontawesome|home"              size={25}              color="#042"              style={{ width: 10, height: 10 }}            />          );        }        if (routeName === 'Chat') {          return (<Image              source={require('../assets/chat.png')}              style={{ width: 10, height: 10 }}            />          );        }        if (routeName === 'Donate') {          return (<Image              source={require('../assets/donate.png')}              style={{ width: 10, height: 10 }}            />          );        }      },    }),  });

HomeScreen.js, by any chance if you want it

import * as React from 'react';import { View } from 'react-native';export default class HomeScreen extends React.Component {  render() {    return(<View>HomeScreen</View>    );  }}

App.js

import * as React from 'react';import { View } from 'react-native';import LoginScreen from './screens/LoginScreen';import SignInScreen from './screens/SignInScreen';import SignUpScreen from './screens/SignUpScreen';import HomeScreen from './screens/HomeScreen';import ForgotPasswordScreen from './screens/ForgotPasswordScreen';import { AppDrawerNavigator } from './components/AppDrawerNavigator';import { createSwitchNavigator, createAppContainer } from 'react-navigation';import { TabNavigator } from './components/TabNavigator';export default class App extends React.Component {  render() {    return(<View><AppContainer /></View>    );  }}const switchNavigator = createSwitchNavigator({  LoginScreen: { screen: LoginScreen },  SignInScreen: { screen: SignInScreen },  SignUpScreen: { screen: SignUpScreen },  HomeScreen: { screen: HomeScreen },  ForgotPasswordScreen: { screen: ForgotPasswordScreen },  AppDrawerNavigator: { screen: AppDrawerNavigator },  TabNavigator: { screen: TabNavigator },})var AppContainer = createAppContainer(switchNavigator)

Please try to solve this error

I have built an app with React Native that works perfectly find in debug mode, but when running the release build it fails when navigating to a scene.

The Xcode console shows a cryptic error message (probably because of minification). I have no idea how to get more out of this error? Is there any way to get more information by bundling differently or looking somewhere else?

[tid:com.facebook.react.JavaScript] TypeError: undefined is not an object (evaluating 'e.default')This error is located at:in rin tin RCTViewin RCTViewin tin tin RCTViewin nin tin nin uin ein tin tin nin ein RCTViewin RCTViewin nin tin inject-t-with-app-userin RCTViewin tin RCTViewin tin RCTViewin RCTViewin n 

Currently I have managed to setup OneSignal properly on Android and iOS. The problem I am encountering however, is that the only devices that are subscribed and showing up in my OneSignal dashboard are the two initial devices. (One which is an emulated Pixel 3 XL and the other which is a real iPhone X) These two devices were setup following the OneSignal React Native documentation here https://documentation.onesignal.com/docs/react-native-sdk-setup

From my understanding, OneSignal automatically subscribes new devices to the dashboard with the OneSignal.init() method or OneSignal.setAppId() method for my case. I am not too sure if I have to have some additional code to support this.

Here is my entry file that works for the 2 initial devices.

index.js (changed app id to the default, to hide my actual one)

React.useEffect(() => {    OneSignal.setAppId('ce8572ae-ff57-4e77-a265-5c91f00ecc4c');    OneSignal.setLogLevel(6, 0);    OneSignal.promptForPushNotificationsWithUserResponse(response => {      console.log(response);    });  }, []);

Thanks for any help!

So we have built a React Native lib which we want to work it with iOS as well.

On Top level, does anyone have idea on how to proceed with (like steps)? and can help me?.

I searched the web but I wasn't able to find anything.

Our Lib only takes initial props which I can pass to RCTrootView.

Jitsi uses react-native to build it's ios App

I am trying to run a React Native Project and it's throwing the following error on react-native run-android.

I have a RN project for version 0.60.4 , to upgrade to version 0.63.3 I created a new project with version 0.63.3 and copied all the files from old project RN Version 0.60.4 to new RN project with version 0.63.3.

After doing the above step its throwing the following error.

Can anyone please help me out as why the issue exists.

Following are the logs:

[Wed May 05 2021 17:04:41.331]  WARN     Require cycle: node_modules/react-native-firebase/dist/utils/apps.js -> node_modules/react-native-firebase/dist/modules/core/app.js -> node_modules/react-native-firebase/dist/utils/apps.jsRequire cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.[Wed May 05 2021 17:04:41.332]  WARN     Require cycle: node_modules/react-native-firebase/dist/modules/admob/index.js -> node_modules/react-native-firebase/dist/modules/admob/Interstitial.js -> node_modules/react-native-firebase/dist/modules/admob/index.jsRequire cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.[Wed May 05 2021 17:04:41.332]  WARN     Require cycle: node_modules/react-native-firebase/dist/modules/admob/index.js -> node_modules/react-native-firebase/dist/modules/admob/RewardedVideo.js -> node_modules/react-native-firebase/dist/modules/admob/index.jsRequire cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.[Wed May 05 2021 17:04:41.333]  WARN     Require cycle: node_modules/react-native-firebase/dist/modules/database/Reference.js -> node_modules/react-native-firebase/dist/utils/SyncTree.js -> node_modules/react-native-firebase/dist/modules/database/Reference.jsRequire cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.[Wed May 05 2021 17:04:41.334]  WARN     Require cycle: node_modules/react-native-firebase/dist/modules/core/firebase.js -> node_modules/react-native-firebase/dist/utils/apps.js -> node_modules/react-native-firebase/dist/modules/core/app.js -> node_modules/react-native-firebase/dist/modules/database/index.js -> node_modules/react-native-firebase/dist/modules/core/firebase.jsRequire cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.[Wed May 05 2021 17:04:41.334]  WARN     Require cycle: node_modules/react-native-firebase/dist/modules/firestore/DocumentSnapshot.js -> node_modules/react-native-firebase/dist/modules/firestore/DocumentReference.js -> node_modules/react-native-firebase/dist/modules/firestore/DocumentSnapshot.jsRequire cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.[Wed May 05 2021 17:04:41.334]  WARN     Require cycle: node_modules/react-native-firebase/dist/modules/firestore/CollectionReference.js -> node_modules/react-native-firebase/dist/modules/firestore/Query.js -> node_modules/react-native-firebase/dist/modules/firestore/QuerySnapshot.js -> node_modules/react-native-firebase/dist/modules/firestore/DocumentChange.js -> node_modules/react-native-firebase/dist/modules/firestore/DocumentSnapshot.js -> node_modules/react-native-firebase/dist/modules/firestore/DocumentReference.js -> node_modules/react-native-firebase/dist/modules/firestore/CollectionReference.jsRequire cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.[Wed May 05 2021 17:04:41.335]  WARN     Require cycle: node_modules/react-native-firebase/dist/modules/firestore/DocumentReference.js -> node_modules/react-native-firebase/dist/modules/firestore/utils/serialize.js -> node_modules/react-native-firebase/dist/modules/firestore/DocumentReference.jsRequire cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.[Wed May 05 2021 17:04:41.335]  WARN     Require cycle: node_modules/react-native-firebase/dist/modules/firestore/utils/serialize.js -> node_modules/react-native-firebase/dist/modules/firestore/FieldValue.js -> node_modules/react-native-firebase/dist/modules/firestore/utils/serialize.jsRequire cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.[Wed May 05 2021 17:04:41.336]  WARN     Require cycle: node_modules/react-native-firebase/dist/modules/core/firebase.js -> node_modules/react-native-firebase/dist/utils/apps.js -> node_modules/react-native-firebase/dist/modules/core/app.js -> node_modules/react-native-firebase/dist/modules/functions/index.js -> node_modules/react-native-firebase/dist/modules/core/firebase.jsRequire cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.[Wed May 05 2021 17:04:41.336]  WARN     Require cycle: node_modules/react-native-firebase/dist/modules/storage/index.js -> node_modules/react-native-firebase/dist/modules/storage/reference.js -> node_modules/react-native-firebase/dist/modules/storage/task.js -> node_modules/react-native-firebase/dist/modules/storage/index.jsRequire cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.[Wed May 05 2021 17:04:41.337]  WARN     Require cycle: node_modules/react-native-paper/src/components/FAB/FAB.js -> node_modules/react-native-paper/src/components/FAB/FABGroup.js -> node_modules/react-native-paper/src/components/FAB/FAB.jsRequire cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.[Wed May 05 2021 17:04:41.337]  WARN     Require cycle: node_modules/react-native-paper/src/components/Appbar/Appbar.js -> node_modules/react-native-paper/src/components/Appbar/AppbarHeader.js -> node_modules/react-native-paper/src/components/Appbar/Appbar.jsRequire cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.[Wed May 05 2021 17:04:41.337]  WARN     Require cycle: node_modules/react-native-paper/src/components/ToggleButton/ToggleButton.js -> node_modules/react-native-paper/src/components/ToggleButton/ToggleButtonGroup.js -> node_modules/react-native-paper/src/components/ToggleButton/ToggleButton.jsRequire cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.[Wed May 05 2021 17:04:41.338]  ERROR    TypeError: undefined is not an object (evaluating '_reactNative.Animated.Text.propTypes.style')[Wed May 05 2021 17:04:41.338]  ERROR    Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication)[Wed May 05 2021 17:04:41.339]  ERROR    Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication)

Package.json

{"name": "FunnyAppName","version": "0.0.1","private": true,"scripts": {"android": "react-native run-android","ios": "react-native run-ios","start": "react-native start","test": "jest","lint": "eslint ."  },"dependencies": {"@yfuks/react-native-action-sheet": "^0.0.5","axios": "^0.19.0","lodash": "^4.17.15","moment": "^2.24.0","native-base": "^2.13.4","prop-types": "^15.7.2","react": "16.13.1","react-native": "0.63.2","react-native-appstore-version-checker": "^3.0.0","react-native-check-box": "^2.1.7","react-native-check-version": "^1.0.8","react-native-complete-flatlist": "^1.1.34","react-native-countdown-component": "^2.5.2","react-native-country-picker-modal": "^2.0.0","react-native-device-info": "^2.3.2","react-native-document-picker": "^4.1.1","react-native-dropdown": "^0.0.6","react-native-dropdown-picker": "^3.7.8","react-native-easy-grid": "^0.2.1","react-native-elements": "^1.1.0","react-native-firebase": "^5.5.6","react-native-flip-toggle-button": "^1.0.9","react-native-floating-action": "^1.21.0","react-native-gesture-handler": "^1.3.0","react-native-hr": "^1.1.4","react-native-image-picker": "^1.0.2","react-native-loading-spinner-overlay": "^2.0.0","react-native-localization": "^2.1.5","react-native-material-dropdown": "^0.11.1","react-native-material-menu": "^1.1.3","react-native-modal": "^11.3.1","react-native-modal-datetime-picker": "^7.5.0","react-native-multiple-choice": "^0.0.8","react-native-multiple-select": "^0.5.3","react-native-multiple-select-list": "^1.0.4","react-native-paper": "^2.16.0","react-native-picker-select": "^6.3.0","react-native-razorpay": "^2.2.4","react-native-reanimated": "^2.1.0","react-native-render-html": "^5.0.0","react-native-screens": "^3.1.1","react-native-select-contact": "^1.2.1","react-native-select-multiple": "^2.0.0","react-native-selectme": "^1.2.3","react-native-simple-radio-button": "^2.7.3","react-native-simple-toast": "^1.1.3","react-native-sqlite-storage": "^5.0.0","react-native-table-component": "^1.2.0","react-native-textarea": "^1.0.3","react-native-vector-icons": "^7.0.0","react-native-version-check": "^3.4.2","react-native-version-info": "^1.1.0","react-native-view-more-text": "^2.1.0","react-native-web-swiper": "^1.16.2","react-native-webview": "^7.5.2","react-native-youtube": "^2.0.1","react-navigation": "^3.11.1","reactstrap": "^8.0.1","rn-fetch-blob": "^0.10.16","rn-multiple-choice": "^0.0.5","toggle-switch-react-native": "^2.0.0"  },"devDependencies": {"@babel/core": "^7.14.0","@babel/runtime": "^7.14.0","@react-native-community/eslint-config": "^2.0.0","babel-jest": "^26.6.3","eslint": "^7.25.0","jest": "^26.6.3","metro-react-native-babel-preset": "^0.66.0","react-test-renderer": "16.13.1"  },"jest": {"preset": "react-native"  }}

Thanks in advance.