Skip to content

fix: swap SafeAreaView for react-native-safe-area-context (closes #539)#577

Open
marcm0de wants to merge 1 commit intoroninoss:mainfrom
marcm0de:fix/swap-safeareaview-for-context
Open

fix: swap SafeAreaView for react-native-safe-area-context (closes #539)#577
marcm0de wants to merge 1 commit intoroninoss:mainfrom
marcm0de:fix/swap-safeareaview-for-context

Conversation

@marcm0de
Copy link
Copy Markdown

Summary

Closes #539 — swaps SafeAreaView from react-native to react-native-safe-area-context in the Container component templates.

Problem

React Native's built-in SafeAreaView only works on iOS and doesn't properly handle notches, dynamic islands, or Android safe areas. The project already uses react-native-safe-area-context (SafeAreaProvider in layout files), but the Container components still import from react-native.

Changes

  • cli/src/templates/base/components/Container.tsx.ejs — Import from react-native-safe-area-context instead of react-native
  • cli/src/templates/packages/nativewindui/components/Container.tsx.ejs — Same change

Why this is safe

react-native-safe-area-context is already a dependency in generated projects (used by SafeAreaProvider in App.tsx/layout files). This is just making the Container component consistent with the rest of the template.

…ontext (closes roninoss#539)

React Native's built-in SafeAreaView only works on iOS and doesn't
properly handle notches/dynamic islands on all devices.
react-native-safe-area-context is already a dependency (used in
SafeAreaProvider in layout files) and is the recommended replacement.

Updated both base and nativewindui Container.tsx.ejs templates.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Swap SafeAreaView for SafeAreaContext

1 participant