Conversation
# Why Follow up to #43365. # How Replaces the hardcoded ccache config with the `setup-ccache` action. # Test Plan Green CI
# Why the default template doesn't depend on `@expo/vector-icons` so it can be removed from package.json # How - remove the dep # Test Plan - create-expo-app with the template, run in on all 3 platforms # Checklist <!-- Please check the appropriate items below if they apply to your diff. --> - [ ] I added a `changelog.md` entry and rebuilt the package sources according to [this short guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
# Why Replace FontAwesome icons with expo-symbols in the Expo tabs template. # How - Replaced `@expo/vector-icons/FontAwesome` with `expo-symbols` SymbolView component - Removed the custom `TabBarIcon` wrapper function and implemented icons directly using SymbolView - Added platform-specific icon names for iOS, Android, and web platforms - Updated the `useColorScheme` hook to handle the 'unspecified' color scheme by defaulting to 'light' (`null` was changed to `unspecified`) - Cleaned up null coalescing operators where the hook now guarantees a non-null return value # Test Plan - create a new app from template, verify it looks good on all platforms # Checklist - [ ] I added a `changelog.md` entry and rebuilt the package sources according to [this short guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
# Why Remove dead code. The `withAndroidSplashLegacyMainActivity` file was no longer used. # How Deleted the plugin source, build output, and its tests. # Test Plan Existing tests still pass / build still success, and no other file is touched. # Checklist - [x] I added a `changelog.md` entry and rebuilt the package sources according to [this short guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) --------- Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com>
# Why The `expo_splash_screen_status_bar_translucent` Android string resource was introduced to let users control whether the status bar was translucent during the splash screen. However, the status bar is always translucent since the `expo-splash-screen` rewrite using the android SplashScreen API. # How - Removed the `expo_splash_screen_status_bar_translucent` string resource from all `strings.xml` files (`bare-expo`, `expo-go`, `minimal-tester`). - Removed the `getStatusBarTranslucent` helper and dropped the `statusBarTranslucent: Boolean` parameter from all `SplashScreen.show` / `ensureShown` overloads. - Renamed `SplashScreenStatusBar.configureTranslucent(activity, translucent)` to `setTranslucent(activity)`, always applying the translucent insets listener. - Same simplification applied to `ExperienceActivityUtils.setTranslucent`. - Removed the corresponding documentation sections from `expo-splash-screen/README.md`. # Test Plan - Launch a managed Expo Go project on Android: the splash screen displays correctly and status bar is translucent. - Launch a bare React Native app (`bare-expo`) on Android: the splash screen displays correctly with no regression. # Checklist - [x] I added a `changelog.md` entry and rebuilt the package sources according to [this short guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) --------- Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )