On Thursday Expo quietly flipped a switch: the latest Expo Go on iOS now refuses to load your project unless you are signed in, in the terminal and in the app. Same week, a 1,036-file React codebase cut its React Compiler build step from 14.3 seconds to 0.81 by switching the compiler to Rust. One change makes your morning slower. The other makes CI cheaper. That is the week.
Here is what mattered in React and React Native for August 31 to September 6, 2026.
Releases
Expo Go now requires login
Posted to the Expo changelog on September 3: the App Store version of Expo Go (which now supports SDK 57) requires you to be logged in to the same Expo account in both the CLI and the app before it will run your project. iOS only for now, Android to follow, simulators exempt, development builds unaffected. I read this as a nudge, not an accident. Expo has been saying for two years that Expo Go is a sandbox and development builds are the real workflow. The friction lands on exactly one person: the newcomer who scanned a QR code from a tutorial and now sees a login prompt instead of their app. If you write onboarding docs, update the screenshots. If you are still deciding what Expo even is, our Expo guide covers the Go versus dev-build split.
The Rust React Compiler is native in Vite
The most upvoted React story on Hacker News this week was a write-up from Master.dev: they moved a 1,036-file React Router codebase to the oxc Rust port of the React Compiler and the compile step went from 14.3s to 0.81s. Whole build 22.1s to 9.3s. The plumbing: oxc shipped official support on August 4, and @vitejs/plugin-react 6.1.0 (August 20) exposes it as react({ compiler: true }) on Vite 8. No Babel plugin, no @rolldown/plugin-babel. The part I care about more than speed: the Rust compiler already handles patterns the Babel 1.0 compiler bailed on, like conditionals inside try/catch and computed object keys. React Native apps still compile through Metro and Babel, so this is a web-side win today. But the direction is obvious.
Expo SDK 57 patches, SDK 58 canaries begin
Expo rolled 57.0.19 on September 1 and 57.0.20 on September 4, and the first 58.0.0-canary builds hit npm on September 2. Canaries are not a release date, but they mark the moment the next SDK starts taking shape in public. If you maintain a native module, this is when you start testing against it.
React Native: a nightly week
No stable React Native release this window. 0.87.1 is still latest and 0.88 nightlies shipped every day. Same story across the stack: React 19.3 canaries daily, Reanimated 4.7 nightlies, Gesture Handler 3.3 nightlies, Screens 4.28 nightlies. Everyone is heads-down between releases. Enjoy it, and use the quiet to finish your Strict TypeScript API migration before the 0.88 opt-out window closes.
Next.js 16.3.4 brings AVIF back
16.3.4 on August 31 re-enables AVIF image optimization after 16.3.3 switched it off, plus fixes for Turbopack manifests and a TypeScript aliasing build error. 15.5.25 landed for the previous major. If you noticed your images got heavier in the last patch, this is why.
Vite 8.3 beta, Bun 1.4.1 and 1.4.2
Vite 8.3.0-beta.0 (September 2) adds a top-level tsconfig option, Rolldown watch options under server.watch, style-tag minification and dead worker chunk removal. Bun 1.4.1 (September 4) closes 202 issues and ships HTTP/2 in Bun.serve, WebSocket pause() and resume(), and a JIT change that drops idle memory: their Next.js SSR benchmark went from 222 MB to 142 MB RSS. Then 1.4.2 the next day fixed two regressions 1.4.1 introduced. Ship fast, patch faster.
Skia 2.11.2, Stream Chat 8.14.1, Storybook 10.6
React Native Skia 2.11.2 (September 1) fixes a framerate bug on React Native Web and a paint anti-aliasing default. Stream Chat React Native 8.14.1 (September 3) is a one-line release: support for React Native 0.85 and up. Two point releases after 0.85 shipped in April. Chat SDKs lag the core more than you would hope; it is one of the things we track in our chat library comparison, and one reason we keep our own @ethora/chat-component on a monthly cadence. Storybook 10.6 (September 2) is all agents: CLI bindings for agent tools and skills, MCP support for Vue and Angular-Vite. An 11.0 alpha also opened.
News
Apple’s September is here: iOS 27 beta 8, Xcode 27 beta 6
iOS 27 beta 8 landed on August 31 and Xcode 27 beta 6 a week earlier. In every year I have shipped iOS apps, beta 8 in the last days of August meant the GM was two weeks out. Run your app on the beta this week, not after the App Store review queue fills up. Watch React Navigation and Screens issues for anything new; the sheet and scroll-edge APIs that arrived with iOS 26 are exactly the surface area that shifts.
Swift’s monthly recap and Embedded Swift 6.4
Swift.org published What’s new in Swift: August 2026 on September 4, two weeks after a preview of Embedded Swift improvements coming in 6.4. Swift 6.3.2 is current. Relevant to us because React Native 0.87 added experimental Swift Package Manager support, and the native side of RN apps is going to look more like Swift and less like CocoaPods over the next year. More on the React Native versus Swift question in a post later this week.
Worth reading
Expo: 12 AEO practices to make your docs AI-ready
Expo’s September 3 post is the most useful documentation piece I have read this year. Their line: agents are now building your React Native apps, so docs have a new species of reader. llms.txt, Markdown at every URL (append .md), stable headings. We run a small docs site ourselves and adopted three of the twelve the same afternoon.
“You don’t need a Mac to build iOS apps anymore”
The top thread on r/reactnative this week is a browser-based iOS simulator with agents driving a camera feature. The best reply: “a Mac in the cloud is still a Mac.” Fair. The genuinely new part is not the missing Mac, it is agents running your simulator for CI-style checks, which is a place React Native testing has always been weak.
That is the week. If I missed something you shipped, or a release that bit you, tell me in the comments and it goes in next Monday’s edition. Half of these digests start there.