Bug Report

Flutter doctor reports "Unable to determine VS Code version" on Red Hat Enterprise Linux with official Microsoft VS Code

Flutter doctor output:

[✓] Flutter (Channel stable, 3.32.5, on Red Hat Enterprise Linux 9.6 (Plow) 5.14.0-570.23.1.el9_6.x86_64, locale en_US) [51ms]
    • Flutter version 3.32.5 on channel stable at /home/vighetti/Strumenti/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision fcf2c11572 (2 weeks ago), 2025-06-24 11:44:07 -0700
    • Engine revision dd93de6fb1
    • Dart version 3.8.1
    • DevTools version 2.45.1

[✓] VS Code (version unknown) [6ms]
    • VS Code at /usr/share/code
    • Flutter extension version 3.114.0
    ✗ Unable to determine VS Code version.

System Info:

• OS: Red Hat Enterprise Linux 9.6 (Plow)
• VS Code installed from official Microsoft repo (NOT code-oss)
• code --version prints:

  1.101.2
  2901c5ac6db8a986a5666c3af51ff804d05af0d4
  x64
  

• which code prints: /usr/bin/code
• Symlink: /usr/bin/code -> /usr/share/code/bin/code
• All permissions are correct (/usr/share/code/bin/code is executable)
• Only one code in PATH
• Flutter doctor run with clean environment (env -i PATH=$PATH HOME=$HOME flutter doctor -v) still shows warning
• All Flutter and VS Code functionality work correctly, only this warning appears

VS Code package details:

Name        : code
Version     : 1.101.2
Release     : 1750797987.el8
Architecture: x86_64
Vendor      : Microsoft Corporation
URL         : https://code.visualstudio.com/

Steps to Reproduce

1. Install VS Code via official Microsoft repo on RHEL 9.6
2. Ensure code is in PATH and code --version works
3. Install Flutter via official instructions
4. Run flutter doctor -v

Expected Result

Flutter doctor detects VS Code version.

Actual Result

Flutter doctor reports:

✗ Unable to determine VS Code version.

Additional notes

• Everything else in Flutter and VS Code works as expected (extensions, debugging, etc).
• The warning is cosmetic, but confusing.
• This may be a detection/compatibility issue with certain Linux distributions or package builds.

Let me know if you need any additional logs or want me to run more diagnostics!