Conversation
# Why This PR updates the Google Play age-signals dependency from version 0.0.2 to 0.0.3 to resolve test failures that were occurring with the previous version, and add new `userStatus` value. https://developer.android.com/google/play/age-signals/release-notes # How Updated the `com.google.android.play:age-signals` # Test Plan - ci, bare expo # 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)
# Why Add support for the `DECLARED` user status in the expo-age-range API documentation to align with the latest Android platform capabilities. # How # Test Plan # 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)
… Dev Launcher (#43518) # Why Following #43514 (removal of `expo_splash_screen_status_bar_translucent` attribute) and #43516 (deletion of `withAndroidSplashLegacyMainActivity`), this PR continues the cleanup by enforcing transparent status bar and navigation bar on Android in Expo Go and dev-launcher (it was already enforced by edge-to-edge, so it's more about removing `backgroundColor` / `translucent` related code). # How - **Expo Go** (`ExperienceActivityUtils.kt`): - Removed `statusBar` `backgroundColor` handling and return value from `setStyle` - Removed `navigationBar` `backgroundColor` handling - Simplified `setStyle` to directly assign `systemUiVisibility` flags without tracking / returning the applied style - Fixed `MANIFEST_NAVIGATION_BAR_VISIBLILITY` → `MANIFEST_NAVIGATION_BAR_VISIBILITY` typo in `ExponentManifest.kt` - **Dev Launcher** (`DevLauncherExpoActivityConfigurator.kt`): - Removed `statusBar` `backgroundColor` / `translucent` handling and return value from `setStyle` - Removed `navigationBar` `backgroundColor` handling - `setTranslucent` no longer takes a `Boolean` parameter (always applies translucent insets) # Test Plan Open the Expo Go / the Bare apps on Android and verify: - Status bar is transparent and respects `barStyle` (`light-content` / `dark-content`) - Navigation bar is transparent - Navigation bar visibility and appearance options still work as expected # 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 - Split `Restore ccache` into separate steps for Android and iOS. - Added `Podfile.lock` to the iOS key - without it, the Ccache hit rate drops, as seen here: https://github.com/expo/expo/actions/runs/22260916981/job/64417320297. - Added Xcode version to the iOS key - each Xcode version introduces changes to the clang compiler (https://gist.github.com/yamaya/2924292), which drops the Ccache hit rate to 0%. # How Implements the above improvements. # Test Plan Green CI
…rectives (#43521) # Why Specifying opt-out directives overrides all defaults, and doesn't add them back. They'll instead have to be added manually; See: https://github.com/facebook/react/blob/e0cc7202e14418b453c69c4f06dc00c64151f202/compiler/packages/babel-plugin-react-compiler/src/Entrypoint/Program.ts#L69-L86 # How - Add list of default directives # Test Plan - Tested manually against local test project - Tested with unit test added in babel-preset-expo # Checklist <!-- Please check the appropriate items below if they apply to your diff. --> - [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: Phil Pluckthun <phil@kitten.sh>
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.
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 : )