NilsBriggen
06519faea2
Two native-only fixes behind the "transcription failed [object Object]" report on the APK: 1. Model download. engineImpl.native.loadModel assumed the ggml .bin was already on disk (the downloader was a TODO), so on a real device it rejected — and since in-app recording is web-only, no model was ever present. Now loadModel fetches the model from Hugging Face (ggerganov/whisper.cpp) into <documentDirectory>/models on first use, reporting 0..1 progress through the existing "Loading model… X%" UI. Downloads to a .part file and renames on success so an interrupted download can't leave a truncated model; if initWhisper still rejects, the file is deleted so the next try re-downloads cleanly. Model URLs verified (tiny.en 77.7MB / base.en 148MB / small.en 488MB). 2. Error surfacing. transcribeStore did `String(err)`, which renders a non-Error native rejection (whisper.rn / file system throw plain objects) as "[object Object]". New shared errorMessage() pulls message/reason/code (or JSON) out of whatever was thrown, so failures are actionable instead of opaque. Progress downloads aren't in the new expo-file-system OO API yet, so the fetch uses the still-supported expo-file-system/legacy resumable downloader; native-only, not bundled on web. Validated: tsc clean, 279 tests pass, web export unaffected (legacy not in the web bundle), arm64 APK builds and the native JS bundle resolves the legacy import. On-device download + transcribe still needs a real phone to confirm end to end. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Other setup steps
- To set up ESLint for linting, run
npx expo lint, or follow our guide on "Using ESLint and Prettier" - If you'd like to set up unit testing, follow our guide on "Unit Testing with Jest"
- Learn more about the TypeScript setup in this template in our guide on "Using TypeScript"
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.