Skip to content
New issue

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

[0.78-stable] Android targetSdk 35 update - remove SafeAreaView and use padding #99

Conversation

alanleedev
Copy link
Collaborator

Cherry-pick commit from PR #95
below is copied from the PR

Summary:

This is an alternative implementation for PR #94 which removes SafeAreaView entirely and uses magic padding for both iOS and Android.

Updating to targetSdk 35 on Android enforces edge-to-edge on Android 15+.
We decided not to use react-native-safe-area-context in the template (PR #84 ) to reduce external dependency although it is the recommendation.
To account for UI overlap, we are using a magic padding value for both iOS and Android in the template.
Also SafeAreaView (iOS only) was removed so same code is used on both platforms.

Changelog:

[ANDROID][CHANGED] - update targetSdk to 35 which will enforce edge-to-edge on Android 15+
[GENERAL][REMOVED] - Removed use of SafeAreaView

Test Plan:

ios_hacky_padding_only.mp4
ios_hacky_padding_only_land.mp4
android_hacky_padding.mp4
android_hacky_padding_land.mp4

@alanleedev alanleedev self-assigned this Jan 14, 2025
@cortinico cortinico merged commit 222da7e into react-native-community:0.78-stable Jan 14, 2025
1 check passed
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.

2 participants