We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If the app is launched from carplay, the insets here will be null which cause SafeAreaProvider doesn't render content
react-native-safe-area-context/src/SafeAreaContext.tsx
Line 78 in b1824ef
The text was updated successfully, but these errors were encountered:
Interesting, I'm not familiar with carplay, I assume it doesn't trigger the same layout events as android which means JS never receive inset values.
Sorry, something went wrong.
@gaodeng I'd be happy to look at PRs
Simply returning the children instead of null fixed it for me. Submitted a PR
diff --git a/node_modules/react-native-safe-area-context/src/SafeAreaContext.tsx b/node_modules/react-native-safe-area-context/src/SafeAreaContext.tsx index 5da007e..6a29480 100644 --- a/node_modules/react-native-safe-area-context/src/SafeAreaContext.tsx +++ b/node_modules/react-native-safe-area-context/src/SafeAreaContext.tsx @@ -100,7 +100,7 @@ export function SafeAreaProvider({ {children} </SafeAreaInsetsContext.Provider> </SafeAreaFrameContext.Provider> - ) : null} + ) : children} </NativeSafeAreaProvider> ); }
Successfully merging a pull request may close this issue.
If the app is launched from carplay, the insets here will be null which cause SafeAreaProvider doesn't render content
react-native-safe-area-context/src/SafeAreaContext.tsx
Line 78 in b1824ef
The text was updated successfully, but these errors were encountered: