d3ro-voice/apps/mobile-rn
Yun Chan 1af3cf75c7
Some checks failed
deploy-site / deploy (push) Failing after 14m16s
fix(release): stop shipping native modules built for the wrong runtime
The released installer could not start: it carried a better-sqlite3 build for the
host Node runtime instead of Electron, so the app died immediately with a module
version mismatch when it opened its database.

Packaging now proves the Electron build of every runtime-sensitive native module
before an installer or archive exists, and installers are produced only from that
verified tree, so the mistake cannot pass silently. The release pipelines run the
same check.

The default local model also pointed at a retired model: a *.gguf name that
Ollama cannot serve, while the settings, onboarding, and guide screens
recommended an older model. All of them now use the model the service code
already preferred.
2026-09-18 15:45:03 +09:00
..
.bundle feat(mobile): Expo → RN CLI 전환 + Android 빌드 성공 2026-04-13 21:13:40 +09:00
.maestro feat(release): prepare 1.1.0 candidate 2026-08-29 18:33:45 +09:00
__mocks__ feat(release): prepare 1.1.0 candidate 2026-08-29 18:33:45 +09:00
__tests__ feat(mobile): keep team, template, and report flows in sync with the server 2026-09-16 23:25:51 +09:00
android fix(release): stop shipping native modules built for the wrong runtime 2026-09-18 15:45:03 +09:00
ios fix(release): stop shipping native modules built for the wrong runtime 2026-09-18 15:45:03 +09:00
metadata/android fix(release): stop shipping native modules built for the wrong runtime 2026-09-18 15:45:03 +09:00
scripts feat(mobile): Expo → RN CLI 전환 + Android 빌드 성공 2026-04-13 21:13:40 +09:00
src feat(mobile): keep team, template, and report flows in sync with the server 2026-09-16 23:25:51 +09:00
.eslintignore feat(release): prepare 1.1.0 candidate 2026-08-29 18:33:45 +09:00
.eslintrc.js feat(release): prepare 1.1.0 candidate 2026-08-29 18:33:45 +09:00
.gitignore feat(release): prepare 1.1.0 candidate 2026-08-29 18:33:45 +09:00
.prettierrc.js feat(mobile): Expo → RN CLI 전환 + Android 빌드 성공 2026-04-13 21:13:40 +09:00
.watchmanconfig feat(mobile): Expo → RN CLI 전환 + Android 빌드 성공 2026-04-13 21:13:40 +09:00
app.json feat(release): prepare 1.1.0 candidate 2026-08-29 18:33:45 +09:00
App.tsx feat(release): prepare 1.1.0 candidate 2026-08-29 18:33:45 +09:00
babel.config.js feat(mobile): Expo → RN CLI 전환 + Android 빌드 성공 2026-04-13 21:13:40 +09:00
Gemfile feat(mobile): Expo → RN CLI 전환 + Android 빌드 성공 2026-04-13 21:13:40 +09:00
index.js feat(release): prepare 1.1.0 candidate 2026-08-29 18:33:45 +09:00
jest.config.js feat(release): prepare 1.1.0 candidate 2026-08-29 18:33:45 +09:00
metro.config.js feat(mobile): Expo → RN CLI 전환 + Android 빌드 성공 2026-04-13 21:13:40 +09:00
package-lock.json fix(release): stop shipping native modules built for the wrong runtime 2026-09-18 15:45:03 +09:00
package.json fix(release): stop shipping native modules built for the wrong runtime 2026-09-18 15:45:03 +09:00
README.md feat(mobile): Expo → RN CLI 전환 + Android 빌드 성공 2026-04-13 21:13:40 +09:00
tsconfig.json feat(updater): overhaul cross-platform auto-update with user consent, blockmap diffs, skip version, and mobile update manager 2026-08-20 22:17:14 +09:00

This is a new React Native project, bootstrapped using @react-native-community/cli.

Getting Started

Note

: Make sure you have completed the Set Up Your Environment guide before proceeding.

Step 1: Start Metro

First, you will need to run Metro, the JavaScript build tool for React Native.

To start the Metro dev server, run the following command from the root of your React Native project:

# Using npm
npm start

# OR using Yarn
yarn start

Step 2: Build and run your app

With Metro running, open a new terminal window/pane from the root of your React Native project, and use one of the following commands to build and run your Android or iOS app:

Android

# Using npm
npm run android

# OR using Yarn
yarn android

iOS

For iOS, remember to install CocoaPods dependencies (this only needs to be run on first clone or after updating native deps).

The first time you create a new project, run the Ruby bundler to install CocoaPods itself:

bundle install

Then, and every time you update your native dependencies, run:

bundle exec pod install

For more information, please visit CocoaPods Getting Started guide.

# Using npm
npm run ios

# OR using Yarn
yarn ios

If everything is set up correctly, you should see your new app running in the Android Emulator, iOS Simulator, or your connected device.

This is one way to run your app — you can also build it directly from Android Studio or Xcode.

Step 3: Modify your app

Now that you have successfully run the app, let's make changes!

Open App.tsx in your text editor of choice and make some changes. When you save, your app will automatically update and reflect these changes — this is powered by Fast Refresh.

When you want to forcefully reload, for example to reset the state of your app, you can perform a full reload:

  • Android: Press the R key twice or select "Reload" from the Dev Menu, accessed via Ctrl + M (Windows/Linux) or Cmd ⌘ + M (macOS).
  • iOS: Press R in iOS Simulator.

Congratulations! 🎉

You've successfully run and modified your React Native App. 🥳

Now what?

  • If you want to add this new React Native code to an existing application, check out the Integration guide.
  • If you're curious to learn more about React Native, check out the docs.

Troubleshooting

If you're having issues getting the above steps to work, see the Troubleshooting page.

Learn More

To learn more about React Native, take a look at the following resources: