flutter_rust_bridge_codegen not found
Seção intitulada “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.
cargo install flutter_rust_bridge_codegenexport PATH="$HOME/.cargo/bin:$PATH"LLVM not found on macOS
Seção intitulada “LLVM not found on macOS”Cause: Flutter Rust Bridge codegen cannot find LLVM.
Fix: Install LLVM with Homebrew.
brew install llvmCocoaPods issues on macOS
Seção intitulada “CocoaPods issues on macOS”Cause: CocoaPods is outdated, missing, or incompatible with the current Xcode version.
Fix: Install or update CocoaPods and reinstall pods.
sudo gem install cocoapodscd iospod deintegratepod installIf needed, clear the CocoaPods cache.
pod cache clean --allrm -rf ~/Library/Caches/CocoaPodsrm -rf ios/Podsrm -rf ios/Podfile.lockcd ios && pod installWindows linker errors
Seção intitulada “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.
rustup default stable-x86_64-pc-windows-msvcAndroid context was not initialized
Seção intitulada “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.
python scripts.py frb --generateflutter cleanflutter pub getiOS TestFlight reports store_dart_post_cobject not found
Seção intitulada “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
Seção intitulada “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.
find ~/Library/Containers -name "nahpu.db" 2>/dev/nullrm /path/to/nahpu.dbfind ~/.local/share -name "nahpu.db" 2>/dev/nullrm /path/to/nahpu.dbGet-ChildItem -Recurse -Path "$env:USERPROFILE\Documents" -Filter "nahpu.db"Remove-Item "$env:USERPROFILE\Documents\nahpu\nahpu.db"adb shellcd /data/data/org.nahpu.app/databasesrm nahpu.db