I am having the same issue. Please help. I am also using react-redux, is that the reason I am getting the error?

react-navigation used old version react-native-safe-area-view for solved this issue you need update on fresh version react-navigation

Trying to find "react-safe-area-view" in node modules to fix this but it doesn't seem to exist in my project.

@fonov I can't update react-navigation right now. Do you know if there's another solution?

Currently upgrading RN Version to 0.63 and using react-navigation 3.3.2.

From StackOverflow, I found that if you remove _component from this.view._component.measureInWindow inside react-native-safe-area-view index file at node_modules, it solves the problem, but it's not a great solution.

@fonov I can't update react-navigation right now. Do you know if there's another solution?

Currently upgrading RN Version to 0.63 and using react-navigation 3.3.2.

From StackOverflow, I found that if you remove _component from this.view._component.measureInWindow inside react-native-safe-area-view index file at node_modules, it solves the problem, but it's not a great solution.

Thanks a LOT enrickdl..It really helped me and the issue is resolveed...

@harrhys Great to hear that! Just FYI, I end it up upgrading react-navigation from v3 to v4, since it's very similar, I didn't have problems and it was very simple. I would suggest that as well.

Sure @enrickdl ..Thans for you suggestion, I will definitely consider upgrading from v3 to v4.
Best Regards,
Harrhy

I found a workaround for this error, without modifying the index of react-native-safe-area-view, at least for my use case.
I'm also using an older version of react-navigation, and update it isn't an option right now.

What I did was to add a resolution in my package.json with react-native-safe-area-view v1.1.0 . Like this:

"resolutions": {
  "react-native-safe-area-view": "1.1.0"
}

Resolutions are only available with yarn: https://classic.yarnpkg.com/en/docs/selective-version-resolutions/

And after that I had to use SafeAreaProvider from react-native-safe-area-context to wrap my app in my entry file:

<SafeAreaProvider>
    <Provider store={store}>
       <AppNavigator  />
    </Provider>
</SafeAreaProvider>

expo SDK: 38
react: 16.11.0
react-native: 0.62.2
react-navigation: 2.18.3

Hope this helps someone.

Thank you @enrickdl - solved my problem too - I'm stuck on an old version of react navigation and must update but really didn't want it to be this month!!!

@matias91 Thank you so muchhhhh
it's work for me with
expo SDK: 38
react: 16.11.0
react-native: 0.62.2
react-navigation: 2.13.0

it didn't work for me
expo SDK:38,
"react-native-paper": "2.16.0"
react-navigation: 4.4.0

@matias91, Thank you for your suggestion on fixing this issue!
It worked for me as well although I forced upgrade the react-navigation@2.0.1 to
react-navigation@2.18.3 since it didn't work on react-navigation@2.0.1.

expo SDK: 39
react: 16.13.1
react-native: 0.63.3
react-navigation: 2.18.3

I found a workaround for this error, without modifying the index of react-native-safe-area-view, at least for my use case.
I'm also using an older version of react-navigation, and update it isn't an option right now.

What I did was to add a resolution in my package.json with react-native-safe-area-view v1.1.0 . Like this:

"resolutions": {
  "react-native-safe-area-view": "1.1.0"
}

Resolutions are only available with yarn: https://classic.yarnpkg.com/en/docs/selective-version-resolutions/

And after that I had to use SafeAreaProvider from react-native-safe-area-context to wrap my app in my entry file:

<SafeAreaProvider>
    <Provider store={store}>
       <AppNavigator  />
    </Provider>
</SafeAreaProvider>

expo SDK: 38
react: 16.11.0
react-native: 0.62.2
react-navigation: 2.18.3

Hope this helps someone.

Not worked for me:
"react": "16.11.0",
"react-native": "0.62.2",
"react-navigation": "2.18.2"
"react-native-safe-area-context": "^3.1.9",