Skip to content

[pull] main from expo:main#599

Merged
pull[bot] merged 6 commits intocode:mainfrom
expo:main
Feb 17, 2026
Merged

[pull] main from expo:main#599
pull[bot] merged 6 commits intocode:mainfrom
expo:main

Conversation

@pull
Copy link

@pull pull bot commented Feb 17, 2026

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 : )

# Why

adds custom sound validation (closes #40954), and improves a push token
warning on simulators

this validates sound resource existence on iOS when calling
`scheduleNotificationAsync`, and on Android when creating a `channel`.

# How

- notification tester app

# Test Plan

via the added examples

# 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)
…r items and bottom tabs (#43185)

# Why

Before the `xcasset` prop was not adjustable for react-native-screens
components. By utilizing the `react-native` loader for loading them we
can now unify the API between toolbar and native tabs


<img height="512" alt="Simulator Screenshot - iPhone 17 Pro - 2026-02-16
at 19 32 48"
src="https://github.com/user-attachments/assets/e22f6a02-6552-4185-949a-3dfceabbd1ad"
/>

# How

When xcasset is rendered in the left or right placement of toolbar or in
native tabs, then pass `src={{ uri: xcasset }}` to
`react-native-screens`

# 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)
# Why

fix jetpack compose doesn't update views

# How

when view is added/removed, we should trigger recompose
# Why

add jetpack compose apis that to support the wiki reader show case

# How

- [core][ui] ad RNHostView as swift-ui
- [core] add `nestedScrollConnection` composableScope that allows descendants to access it
- [core] add Children with filter support. that to support SlotView for compound components
- [core] add `onGlobalEvent` as default registered event. this aligns with swift-ui implementation and to support `modifier.clickable(() => { ... })`
- [core] `RecordTypeConverter` to support convertFromMap with nested map
- [ui] add Icon which supports loading material symbol xml, e.g. `<Icon source={require('./path/to/symbol.xml'} />`. that to align modern material symbol usage.
- [ui] add BasicAlertDialog (m3 api), Card, FlowRow, DockedSearchBar, SearchBar, FilterChip (for aligned naming), HorizontalFloatingToolbar, LazyColumn, ListItem, PullToRefreshBox, RadioButton (for aligned naming), Spacer, Surface, ToggleButton
- [ui] add modifiers: width, height, wrapContentWidth, wrapContentHeight, align, clickable, selectable
- [ui] rename BottomSheetView to ModalBottomSheet that to align compose api naming 
- [ui] change clip modifier usage. remove the coupling from Shape component and use predefined constants directly. e.g. `clip(Shapes.RoundedCorner(16))`
- [ui] support `<Switch.ThumbContent>`
- [ui] add broder style support for Text

---------

Co-authored-by: nishan (o^▽^o) <nishanbende@gmail.com>
# Why

Starting from SDK 55 dev menu can be used as a standalone pacakge and
thus we should document it

# How

Add dev-menu package docs

# Test Plan

n / a

# 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)

---------

Co-authored-by: Aman Mittal <amandeepmittal@live.com>
@pull pull bot locked and limited conversation to collaborators Feb 17, 2026
@pull pull bot added the ⤵️ pull label Feb 17, 2026
@pull pull bot merged commit 60d4a5f into code:main Feb 17, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

Comments