* fix(app): restore a host's workspaces after its cached directory is evicted A host could keep a current directory checkpoint in the replica cache with none of the rows it described. The daemon then answered "no changes" since that cursor, and the sidebar had no projects to place cached workspaces under, so every workspace for that host vanished and stayed missing across restarts. The cache already refused mutations for an evicted host, but it checked at the moment a mutation was queued. Eviction happens later, inside the serialized write, so anything queued before the eviction ran was still written, checkpoint included. The check moves into materializePendingChanges so it runs in the same serialized step that evicts, which also covers an eviction that lands while an earlier persist is still indexing the store. Checking at queue time was also losing good data: once a host was invalidated, every mutation was dropped, including updates accepted between a reconnect's baseline replacement and its write. Those are kept now, because the baseline is in the same pending batch. Version 1 checkpoints could have been written by that path, so they are no longer trusted. A reader discards them and keeps the cached rows, so the sidebar still paints from cache and each host re-syncs its directory once. Later launches resume incrementally. Both the race and the recovery live in the shared cache, so this covers iOS, Android, web, and Electron. It does not address two tabs or windows sharing one IndexedDB database, where another connection evicts the host. * fix(app): hold workspace updates that arrive while the directory cache loads A project update received while the cached directory was being read went straight into the replica. It advanced the project cursor before any refresh had established a baseline, and saved that cursor to the cache. On an install damaged before the eviction fix, that write replaced the version 1 checkpoint with a version 2 one before the reader could reject it. The refresh then asked for project changes after the live update, the daemon had none, and projects missing from the cache stayed missing across restarts. Agents already open a transaction before the cache load, so their updates are recorded and applied over the refreshed snapshot. Workspaces now do the same. An update during the load also stops the cached cursors being adopted, so the refresh fetches full snapshots, which is the recovery a damaged cache needs. * fix(app): advance directory cursors from live updates only after a refresh A live update moved the directory cursor whenever no refresh was in flight, including when no refresh had ever completed on the current subscriptions. If the first sync after discarding a version 1 checkpoint failed, the next project update saved a cursor at its own sequence with only that project stored. The retry asked for changes after it, the daemon had none, and the other projects stayed missing across restarts. The previous commit closed this window during the cache load only; a failed refresh reopened it. A live event's sequence covers everything before it only when a refresh completed on the subscriptions that delivered it, which is what satisfiedDemandSource already records. Live events now update rows either way but move the cursor only in that state, so a cursor never skips changes the client did not receive. Once a refresh completes, live updates advance the cursor as before. The sidebar recovery e2e fixture unwrapped the checkpoint only when it was version 1, so the version 2 writer made it abort before damaging the cache. It now reads either envelope and stores the damage as version 1, the format this branch stops trusting, so the test fails against the previous cache module and passes here. * fix(app): apply the eviction rule to malformed-row repairs Repairing a malformed directory row reads the checkpoint, drops the affected cursor, and writes the rest back. That write went straight to the row store through queueOperation, outside the eviction check in the regular persist path. If a write evicted the same host while the repair was reading, the repair stored a checkpoint for a host with no directory rows, the state this branch exists to prevent. All three repair writes now go through one helper that runs in the serialized writer and drops the checkpoint upsert when the host has been evicted since. The deletes still apply. * fix(app): record a host eviction only after its delete commits Eviction marked the host as evicted before deleteHost ran. If storage aborted that delete, the rows stayed stored but the mark remained. A malformed-row repair running behind it trusted the mark: it skipped the checkpoint update yet still deleted the row, leaving a workspace cursor with no workspace. The next refresh then resumed past that workspace. The mark is now set after the delete commits, so it always matches storage. A failed eviction leaves no mark, and the repair updates the row and its cursor together.
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.