Conversation
… null (#43336) ## Why `Color.android.dynamic.background` always returns `null` on Android while other dynamic colors like `onBackground`, `surface`, etc. work correctly. The `"background"` key was missing from the `attrMap` in `ExpoRouterModule.kt`. Fix for issue: #43302 ## How Added `"background" to android.R.attr.colorBackground` to the `attrMap` in `ExpoRouterModule.kt`. The Material library does not define its own `colorBackground` attribute (it only defines `colorOnBackground`), so we use the framework's `android.R.attr.colorBackground` which Material3 themes define. ## Test Plan 1. Create a project using `Color.android.dynamic.background` from `expo-router` 2. Run on Android device/emulator with `npx expo run:android` 3. Verify `Color.android.dynamic.background` returns a hex color value instead of `null` Co-authored-by: Jakub Tkacz <32908614+Ubax@users.noreply.github.com>
) # Why This aligns our minimum version of hermes-parser / babel-plugin-syntax-hermes with the pinned versions of react-native and metro. While it's unfortunate they're pinned and we don't have all the details here, we should make sure the minimums match, to not break the minimum support that React Native assumes. This might be important for Hermes v1. I don't want to match the pin here since that'd mean it's difficult to allow patches/updates and it's unlikely we can accurately keep this in sync. Some of the pins in metro/RN are for dangling dependencies and unused. We can probably revisit this, but this will also require changes in metro/RN. # How - Bump ranges of `hermes-parser` and `babel-plugin-syntax-hermes-parser` to `^0.32.0` # Test Plan - CI should pass. E2E are especially important for this change # 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)
) ## Summary - When a module name conflicts with an Apple framework (e.g., `MultipeerConnectivity`), automatically prefix it with "Expo" to avoid iOS build errors - Warns the user about the rename with a clear message ## Test plan - `yarn test` passes - Run `npx create-expo-module --local multipeer-connectivity` and verify the module name is renamed to `ExpoMultipeerConnectivity` with a warning 🤖 Generated with [Claude Code](https://claude.ai/code) Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
This reverts commit 64bb709.
expo-widgets@55.0.1 @expo/ui@55.0.1 expo-sqlite@55.0.10 expo-router@55.0.1 expo-modules-core@55.0.12 expo-module-template-local@0.7.8 expo-module-template@55.0.8 expo-dev-menu@55.0.9 expo-dev-launcher@55.0.10 expo-camera@55.0.9 expo-brownfield@55.0.11 babel-preset-expo@55.0.8 @expo/metro-config@55.0.9 expo@55.0.1 @expo/cli@55.0.12 expo-template-tabs@55.1.8 expo-template-default@55.1.8 expo-dev-client@55.0.9 expo-template-bare-minimum@55.0.13
expo-template-blank-typescript@55.1.8 expo-template-blank@55.1.8
… 55 (#42841) Co-authored-by: Kadi Kraman <kadi@expo.io>
…ired --environment flag in SDK 55 (#43383)
Co-authored-by: Kadi Kraman <kadi@expo.io>
Co-authored-by: Jakub Tkacz <32908614+Ubax@users.noreply.github.com> Co-authored-by: Kadi Kraman <kadi@expo.io>
…r SDK 55 (#42883) Co-authored-by: Jakub Tkacz <32908614+Ubax@users.noreply.github.com>
# Why <!-- Please describe the motivation for this PR, and link to relevant GitHub issues, forums posts, or feature requests. --> # How <!-- How did you build this feature or fix this bug and why? --> # Test Plan <!-- Please describe how you tested this change and how a reviewer could reproduce your test, especially if this PR does not include automated tests! If possible, please also provide terminal output and/or screenshots demonstrating your test/reproduction. --> # 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)
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.
7 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 : )