Conversation
# Why Fixes two main problems with the brightness test suite: On iOS: The system didn't have time to update the brightness value, causing: <img width="345" height="66" alt="Screenshot 2026-05-07 at 21 52 45" src="https://github.com/user-attachments/assets/ad1d2cf8-462e-4099-b121-31daff0f0828" /> On Android: There was a problem with the epsilon: <img width="323" height="98" alt="Screenshot 2026-05-07 at 21 47 31" src="https://github.com/user-attachments/assets/fdb43a0b-e89c-4531-99b2-9f3761ab0c80" /> # How - Added `timeoutWrapper`, to give the system time to update the brightness - Added a correct epsilon for Android # Test Plan BareExpo ✅
…s causing images to disappear (#45467)
# Why The current [Using Clerk](https://docs.expo.dev/guides/using-clerk/) guide is a brief stub that links out to Clerk's quickstart and predates `@clerk/expo` Core 3. It also predates the new native UI components (`<AuthView />`, `<UserButton />`, `<UserProfileView />`) that ship with `@clerk/expo/native` and the native social sign-in hooks (`useSignInWithGoogle()`, `useSignInWithApple()`). This PR replaces the page with a complete getting-started guide that: - Explains the three integration approaches Clerk now supports on Expo (JS only, JS + native social sign-in, and native UI components) and which one to pick. - Shows the install + `<ClerkProvider>` setup that works for `@clerk/expo` 3.x (Expo SDK 53–55). - Walks through a minimum sign-in screen for each of the three approaches. - Covers reading the signed-in user with `useUser()`, `useAuth()`, and the new `<Show>` control component. - Links out to Clerk's reference docs for deeper topics (Sign in with Google/Apple, deployment, etc). # How - Replaced `docs/pages/guides/using-clerk.mdx` with the new content. - Verified every API reference against the current `@clerk/expo` source (peer deps, exported hooks, `<ClerkProvider>` props, `useSignIn()` / `useSignUp()` Core 3 signal shape, `<AuthView />` props, `useUserProfileModal()` return). - Verified code examples against the Clerk team's reference quickstarts (`JSOnlyQuickstart`, `JSWithNativeSignInQuickstart`, `NativeComponentQuickstart`) and the canonical partials in `clerk-docs` so the patterns stay consistent across docs. - Built locally with `pnpm dev` and reviewed the rendered page at `http://localhost:3002/guides/using-clerk/`. # Test Plan - `cd docs && pnpm dev` and open http://localhost:3002/guides/using-clerk/ — page renders, code blocks highlight, tabs/steps work, all `<BoxLink>` cards link to existing Clerk doc pages. - No links into `expo/expo` itself were changed. # Checklist - [x] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] I added a `changelog.md` entry — N/A, docs-only change - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build — N/A, docs-only change --------- Co-authored-by: Aman Mittal <amandeepmittal@live.com>
…vigation (#45543) # Why After #45241 was merged, I forgot to adjust the rewrite in the metro plugin. At the moment it incorrectly rewrites `@react-navigation/core` imports to `expo-router` instead of `expo-router/react-navigation` # How Change `return doResolve('expo-router');` to `return doResolve('expo-router/react-navigation');` # Test Plan Local project with `react-native-screens-transition` (or any other third-party navigator) installed # 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 The new `expo-file-system` API reference was missing important guidance for task-based downloads/uploads and file picking. This improves the generated docs so users can understand task lifecycle, progress, cancellation, pause/resume, and picker result shapes without reading the source. # How - Added TSDoc coverage for download/upload task APIs, including constructors, state transitions, progress listeners, cancellation, pause/resume, and saved download state. - Improved `pickFileAsync` overload docs, added a multiple-file example, and used docs inlining to reduce helper-type noise in generated API data. - Hid `DEFAULT_DEBOUNCE_MS` from public docs, documented the watcher default as `100`, exported `RelocationOptions`, and marked file-system native task types as non-linkable to avoid broken API links. - Updated `@docsInline` generation to recognize Expo custom doc tags during its TypeDoc side pass, then regenerated `expo-file-system` API data and package declarations. > **NOTE:** There are some unnecessary methods coming from `SharedObject` _(our API generation doesn't filter them out well when SharedObject is a grandparent class)_. I get rid of them in the upstack PR # Test Plan 1. Run `et gdad -p expo-file-system` 2. Run `pnpm --filter expo-file-system run build` and verify the package declaration output is rebuilt successfully. 3. Open docs locally and verify the download/upload task docs, `pickFileAsync` overload example, `RelocationOptions` links, and watcher debounce default render 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). - [x] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
…cks (#45550) # Why The `VCS_DIRECTORIES` check was embedded in `ignorePattern` and is often redundant or redundantly applied, given that it's a fixed pattern that can be applied as needed. Especially in the Node crawler's hot path, it's a check we can just inline, since we have all necessary data already. Some checks were performed unnecessarily, instead of constructing smaller, fixed predicates once. This also applied to the "health check file prefix" check (for health checking the watcher), which isn't enabled by default and hence entirely redundant. # How - Embed and localize VCS directory checks, as possible/needed, and remove regex modification - Make health-file check conditional and remove its use of `path.basename` # Test Plan - Unit tests added to capture changes # 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)
…5555) # Summary - Adds `experiments.onDemandFilesystem` # 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. --> - [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)
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.
10 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 : )