When first running cargo android run I found that it tried to run adb internally but didn't find the executable (since it's not in my PATH). It could be good if cargo-mobile didn't depend on the PATH being configured for SDK tools since it should be able to find them based on the the SDK path instead I think.
When first running
cargo android runI found that it tried to runadbinternally but didn't find the executable (since it's not in my PATH). It could be good ifcargo-mobiledidn't depend on the PATH being configured for SDK tools since it should be able to find them based on the the SDK path instead I think.