Lewati ke konten
Dokumentasi NAHPU

Troubleshooting

Konten ini belum tersedia dalam bahasa Anda.

flutter_rust_bridge_codegen not found

Section titled “flutter_rust_bridge_codegen not found”

Cause: flutter_rust_bridge_codegen is not in your PATH.

Fix: Install it and ensure Cargo binaries are available to your shell.

Terminal window
cargo install flutter_rust_bridge_codegen
export PATH="$HOME/.cargo/bin:$PATH"

LLVM not found on macOS

Section titled “LLVM not found on macOS”

Cause: Flutter Rust Bridge codegen cannot find LLVM.

Fix: Install LLVM with Homebrew.

Terminal window
brew install llvm

CocoaPods issues on macOS

Section titled “CocoaPods issues on macOS”

Cause: CocoaPods is outdated, missing, or incompatible with the current Xcode version.

Fix: Install or update CocoaPods and reinstall pods.

Terminal window
sudo gem install cocoapods
cd ios
pod deintegrate
pod install

If needed, clear the CocoaPods cache.

Terminal window
pod cache clean --all
rm -rf ~/Library/Caches/CocoaPods
rm -rf ios/Pods
rm -rf ios/Podfile.lock
cd ios && pod install

Windows linker errors

Section titled “Windows linker errors”

Cause: MSVC build tools or the Windows SDK are missing or misconfigured.

Fix: Install Visual Studio Build Tools with the Desktop development with C++ workload, then use the MSVC Rust toolchain.

Terminal window
rustup default stable-x86_64-pc-windows-msvc

Android context was not initialized

Section titled “Android context was not initialized”

Cause: The Dart VM loads the Rust library differently than a standard Android JVM app.

Fix: Check the current Flutter Rust Bridge Android setup and regenerate the bridge files. This error usually means the Android native loading path is out of sync with the bridge configuration.

Terminal window
python scripts.py frb --generate
flutter clean
flutter pub get

iOS TestFlight reports store_dart_post_cobject not found

Section titled “iOS TestFlight reports store_dart_post_cobject not found”

Cause: Xcode stripped symbols needed by Flutter Rust Bridge.

Fix: In Xcode, open the build settings for the native Rust target. Under Deployment, set Strip Linked Product to No and Strip Style to Debugging Symbols.

App stuck on home screen after schema changes

Section titled “App stuck on home screen after schema changes”

Cause: A schema change was made without a matching version bump, generated code update, or migration.

Fix for development: Confirm the database path and follow the schema and migration workflow in Persistence data. Delete only the local development database and rerun the app. For production changes, add a real migration.

Terminal window
find ~/Library/Containers -name "nahpu.db" 2>/dev/null
rm /path/to/nahpu.db