Grails应用执行grails run-app时无法自动启动浏览器问题求助

Got it, let's walk through the likely reasons your Grails app stopped auto-opening the browser when running grails run-app—even without code changes, Git issues or system-level tweaks could be the culprit:

• Accidental configuration changes (even via Git)
  Even if you didn't edit code manually, Git operations like a messy merge auto-resolve, an accidental reset, or a teammate's config commit you pulled might have flipped a key setting. Check your grails-app/conf/application.yml or application.groovy for lines like grails.run.autoLaunch: false—that's the main toggle for auto-launch. Also, double-check system environment variables: if GRAILS_AUTO_LAUNCH is set to false anywhere, that'll override your config files.

• Git repository corruption
  You mentioned Git might be damaged, so start with checking repo health. Run git status to see if config files have uncommitted changes you didn't notice. If you suspect corruption, run git fsck to scan for underlying issues. If the config files look off, restore them to the last known working commit with git restore grails-app/conf/application.yml (adjust the file path as needed for your setup).

• System browser association issues
  Grails relies on your system's default browser to launch. If you recently changed your default browser, uninstalled it, or it has broken file associations, Grails might fail to trigger it. First, test if your app is actually running by manually opening http://localhost:8080 (or your custom port) in a browser. If it loads, try forcing the launch with grails run-app --launch-browser to see if that bypasses the issue.

• Corrupted Grails/dependency cache
  Over time, local build caches can get messed up. Run grails clean to wipe old build artifacts, then try grails run-app again. For Grails 4+ (which uses Gradle under the hood), you can also run ./gradlew clean bootRun to rule out Gradle-specific cache problems. Double-check your gradle.properties to make sure the Grails version hasn't changed unexpectedly (auto-updates are rare but possible if you're using a dynamic version tag).

• Port conflicts or security blocks
  If a leftover Grails process is hogging your default port (usually 8080), the new app instance might start silently without triggering the browser. On Mac/Linux, run lsof -i :8080; on Windows, use netstat -ano | findstr :8080 to find and kill the stuck process. Also, check if your firewall or antivirus is blocking Grails from launching external apps like browsers—temporarily disabling them (carefully!) can help test this.

内容的提问来源于stack exchange，提问作者Peter Cook