react-native-safe-area-view | ️ Deprecated : use the successor react

Issue solved. Just deleted node_modules and cleared yarn cache. Reinstalled node_modules and it worked.

Are you try: cd ios && pod install && cd .. Then close app, close all terminal and rebuild your app. Hope help you.

It seems to be an error in case, it should be StyleSheet and not Stylesheet

It seems that the problem was in the "keyboard-aware-scroll-view" package and here is the comment that actually fixed my issue: https://github.com/APSL/react-native-keyboard-aware-scroll-view/issues/440#issuecomment-699653218

As @AkilaDevinda suggested I looked for clean in code and found that I am using cleanExtractedImagesCache() function from library react-native-image-filter-kit.

Issue was that I had disabled auto-link for android in react-native.config.js

Look like cleaning expo cache helped

expo r -c

expo r --help

Except for the one in react-native they build on top of one another. All the others instruct that you need to wrap your whole app inside a SafeAreaProvider component.

I dug into the source code a bit and this is my deductions:

The default implementation provided with React Native. Should work for most cases but doesn't e.g. provide inset amounts programmatically.

Provides detailed, retrievable inset information and a rather bare-bones implementation of SafeAreaView.

Written on top of react-native-safe-area-context, it re-exports SafeAreaProvider and various other methods, but provides a more complex/fancy implementation of SafeAreaView that uses Animated.View. Adds properties such as forceInset to avoid jankiness in some cases due to layout updates. Implemented by the React Navigation team.

Re-exports SafeAreaView from react-native-safe-area-view for convenience and is functionally equivalent. (The same is also exported by @react-navigation/native).

1. If you don't use React Navigation and don't have special needs, use SafeAreaView from react-native. It's provided by default and works.
2. If you don't use React Navigation but need more functionality, use react-native-safe-area-context or react-native-safe-area-view depending on your needs.
3. If you're using React Navigation, use the one from react-navigation or react-native-safe-area-view. It just may work better with React Navigation. Both are equivalent, choose one and use it consistently.

I recommend adding an ESLint no-restricted-imports rule that forbids accidentally importing SafeAreaView from any other location than the one you chose to use.

About the warning.

Yellow Warnings in react-native discloses inefficient code in your application which eventually leads to a performance issue or increase in memory consumption.

Yes, the warning nesting VirtualizedList inside a plain ScrollView is bad for your app.

This usually happens while rendering Flatlist inside a ScrollView. (from your import)

• Flatlist fails to calculate the size of the current window and will try to render everything at the same time which leads to a performance problem.

How to get rid of the warning

It's easy to resolve this issue just remove the ScrollView and move the components around Flatlist to ListHeaderComponent and ListFooterComponent

If you export default you need to import the entire file. Your fix would be to change the import in the Navigator.js from:

import {HomeScreen} from '../' to import HomeScreen from '../'