CtrlCreeper
e8108d9092
* fix(app): only offer Remove for providers defined in config.json Plugin-registered providers (Antigravity, Muse Code) share source: "custom" with config-defined ones, so Settings → Providers offered Remove on them. The removeProviders patch only deletes config.json entries, so the action succeeded silently while the plugin re-registered the provider. Gate the Remove menu on the provider having an extends entry in config — the actual definition custom providers live behind. Plugin providers keep their enable/disable switch. Fixes #6349 * Address review: named ownership check, E2E coverage for plugin providers - Name the config-owned provider check instead of combining three conditions inline in canRemove. - Replace the JSDOM component tests with a Playwright case in the existing provider-removal suite: a plugin-registered provider renders without the Remove action and survives a removeProviders patch.
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.