Mohamed Boudra
0474c3e0af
The mock provider splits "**Bold" into two frames, "**Bo" and "ld". The helper forwarded both back-to-back and asserted the strong span reads "Bold", which only holds when the browser commits both frames to the store in one reducer flush and the message first mounts with "**Bold". When a frame boundary lands between the two tasks the message mounts with "**Bo" and word pacing holds "ld" until the whitespace after it arrives, so the span reads "Bo" until the gate releases. That is the designed behaviour of the reveal, and the batching is up to the browser's task scheduling. Stop after "**Bold text" instead: the space after "Bold" ends the word, so every batching reveals "Bold" and never more than "text". Forcing the frames into separate commits reproduced the CI failure before the change and passes after it.
Welcome to your Expo app 👋
This is an Expo project created with create-expo-app.
Get started
-
Install dependencies
npm install -
Start the app
npx expo start
In the output, you'll find options to open the app in a
- development build
- Android emulator
- iOS simulator
- Expo Go, a limited sandbox for trying out app development with Expo
You can start developing by editing the files inside the app directory. This project uses file-based routing.
Get a fresh project
When you're ready, run:
npm run reset-project
This command will move the starter code to the app-example directory and create a blank app directory where you can start developing.
Learn more
To learn more about developing your project with Expo, look at the following resources:
- Expo documentation: Learn fundamentals, or go into advanced topics with our guides.
- Learn Expo tutorial: Follow a step-by-step tutorial where you'll create a project that runs on Android, iOS, and the web.
Join the community
Join our community of developers creating universal apps.
- Expo on GitHub: View our open source platform and contribute.
- Discord community: Chat with Expo users and ask questions.
Dictation debugging
Set EXPO_PUBLIC_ENABLE_AUDIO_DEBUG=1 before running npx expo start to render the in-app audio debug card. Pair it with the server-side STT_DEBUG_AUDIO_DIR flag so every dictation includes a copyable path to the saved raw audio file.