quasarframework/quasar · error
Cannot determine path to IDE executable
Error message
Cannot determine path to IDE executable
What it means
On Linux, when launching an IDE for a Capacitor target, runLinux cannot find the Android Studio executable because quasar.config > bin > linuxAndroidStudio is not set (or points to a non-existent path). The tool warns, prints instructions, and exits with code 1 since it cannot open the IDE.
Source
Thrown at app-vite/lib/utils/open-ide.js:84
function runLinux(mode, bin, target, appPaths) {
if (target === 'android') {
const studioPath = getLinuxPath(bin)
if (studioPath) {
const folder =
mode === 'cordova'
? appPaths.resolve.cordova('platforms/android')
: appPaths.resolve.capacitor('android')
return open(folder, {
app: { name: studioPath },
wait: false
})
}
} else if (target === 'ios') {
fatal('iOS target not supported on Linux')
}
warn('Cannot determine path to IDE executable')
console.log(
' Please set quasar.config file > bin > linuxAndroidStudio with the escaped path to your studio.sh'
)
console.log(" Example: '/usr/local/android-studio/bin/studio.sh'")
process.exit(1)
}
function getWindowsPath(bin) {
if (bin.windowsAndroidStudio && fs.existsSync(bin.windowsAndroidStudio)) {
return bin.windowsAndroidStudio
}
const studioPath = String.raw`C:\Program Files\Android\Android Studio\bin\studio64.exe`
if (fs.existsSync(studioPath)) {
return studioPath
}
try {View on GitHub (pinned to 4841521b5f)
Solutions
- Set quasar.config > bin > linuxAndroidStudio to the absolute path of studio.sh.
- Verify the file exists and is executable (e.g. ls -l /path/to/studio.sh).
- Re-run the command; if it still fails, locate studio.sh with 'which studio.sh' or inside the android-studio install directory.
Example fix
// before (quasar.config)
bin: {}
// after
bin: { linuxAndroidStudio: '/usr/local/android-studio/bin/studio.sh' } Defensive patterns
Strategy: validation
Validate before calling
import { existsSync } from 'node:fs';
const p = cfg.bin?.linuxAndroidStudio;
if (!p || !existsSync(p)) throw new Error(`linuxAndroidStudio not set or missing: ${p}`); Prevention
- Always set quasar.config > bin > linuxAndroidStudio on Linux dev machines.
- Check the studio.sh path with ls -l before relying on IDE-open commands.
- Document per-machine paths in local (untracked) config or a setup script.
When it happens
Trigger: Running a command that opens the IDE for android target on Linux (via openIDE -> runLinux) while quasar.config has no bin.linuxAndroidStudio value, or the configured studio.sh path does not exist.
Common situations: Fresh project on Linux where Android Studio was installed via snap/flatpak so studio.sh lives in a nonstandard path; team config never sets the bin section; switching machines with different install locations.
Related errors
- [Quasar] In your Vite config file, please add the Quasar plu
- Failed to open specific browser
- Specified profile file has a syntax error
- quasar.config file > invalid Vite plugin specified (cannot f
- The file defined in quasar.config > bex > extraScripts > "${
AI-assisted analysis of quasarframework/quasar@4841521b5f (2026-08-30).
Data as JSON: /api/errors/80ce5242d908b067.
Report an issue: GitHub.