Tauri mobile debugging (Android/iOS)
#1268
Replies: 1 comment
-
|
CodeLLDB expects cargo to build the target binary and output it's location in JSON format, so it knows what to launch. Unless the By default, when remote debugging, LLDB will deploy your binary to the target device, so you can use standard |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to setup a proper debugging experience for my tauri project. The desktop target works fine, but the Android target doesn't. Here's my
launch.jsonfile:{ "type": "lldb", "request": "launch", "name": "Desktop Development", "cargo": { "args": [ "build", "--manifest-path=./frontend/splitfire-desktop/src-tauri/Cargo.toml", "--no-default-features" ] }, // task for the `beforeDevCommand` if used, must be configured in `.vscode/tasks.json` "preLaunchTask": "ui:dev" }, { "type": "lldb", "request": "launch", "name": "Android Development", "program": "cargo", "args": [ "tauri", "android", "dev" ], "cwd": "${workspaceFolder}/frontend/splitfire-desktop", "env": { "RUST_LOG": "debug" }, "sourceLanguages": ["rust"] },I can't use the official cargo support per this docs because
tauricli is a cargo subcommand. Or maybe I missed something.I could probably use the cargo support, but when I set it up like this:
I got error:
Any pointer?
Beta Was this translation helpful? Give feedback.
All reactions