Open lindongchen opened 6 months ago
As far as i know, sidecars are simply not supported on mobile. I hope we can improve the errors somehow though 🤔
Can I call it with a rust code snippet like this Command::new("./src-tauri/bin/pipy")
I don't think the binary is even included in the apk/aab so no. In a general sense, the path must point to where the file is after installation, so no src-tauri mention.
Thanks, I understand that. Will the upcoming version plan to fix this issue? Or you have any other suggestions
It's not planned right now but it's not a definite "no, never" yet. Either way I doubt that it will be part of the initial 2.0 Release.
When I manually copy the binary to src-tauri/gen/android/app/src/main/assets, it can be displayed in Android Studio, so can I try calling it using Command.sidecar or Command.create?
@FabianLars We need to give a note on Embedding External Binaries page about iOS & Android unsupport.
Describe the bug
Error: Uncaught (in promise) No such file or directory (os error 2) Event: Command.sidecar("bin/pipy", args) ...call sidecar Sidecar position: src-tauri/bin/pipy-aarch64-linux-android Sidecar package position: src-tauri/target/aarch64-linux-android/debug/pipy Sidecar bundle: tauri.conf.json => bundle > "externalBin": ["bin/pipy"]
Simply put, I saw that the sidecar had been packaged in a reasonable location, but when running on the Android emulator, I couldn't find the file. What I can confirm is that other programs can run as usual, and on Mac OS and Windows, my sidecar still works as usual, but it can't be found on the Android emulator
Here is my Cargo.toml configuration:
Reproduction
No response
Expected behavior
No response
Full
tauri info
outputStack trace
No response
Additional context
No response