tree 09a3d540cc7da4bf0c9df26a2a72f9bd7b95921d
parent e34d6bc6911a15145ff2f06d1401d15ca7b5a747
author Loïc Sharma <737941+loic-sharma@users.noreply.github.com> 1656630920 -0700
committer GitHub <noreply@github.com> 1656630920 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJivi6ICRBK7hj4Ov3rIwAAuFIIAKbfLuy6aOloZOh9qy6GSDEM
 EsNajoV7G4iy4QaTbAUxIDz9Cidkx+GxDbzTQII+1MOGt2d8AKdxk7WkQrBw/zHb
 lu6A2F6gIjKKAn3dzzzc7hIyOxn6kjPT/jypn0bkJxZ+6K6D71/OpWSWTIFxbcyk
 nFUIvqJUbOIIT4uIntqNyApJcJhqDF/jXOclpdNyd/XvHVzyxfwcVSCWCbSWI0xx
 XFiiv/Z6ftm2M0HKg0zoHgce71zCs4f3k/DhqMrWoDdY8fHo2vxbKLPeSPOCxl6g
 krEP9Jr1Iq5e2JMYrtjNoB6r1J1sxMbgSla5KtqIaW5uCZJ1ScFaiSMjW0cIYhA=
 =YoyN
 -----END PGP SIGNATURE-----
 

Ignore invalid description property in vswhere.exe JSON output (#106836)

The `flutter doctor` command uses `vswhere.exe` to verify the Visual Studio installation. This `vswhere.exe` is known to encode its output incorrectly. This is problematic as the `description` property is localized, and in certain languages this results in invalid JSON due to the incorrect encoding.

This change introduces a fallback to our `vswhere.exe` output parsing logic: if parsing JSON fails, remove the `description` property and retry parsing the JSON.

This fix was also tested on the outputs provided here: https://github.com/flutter/flutter/issues/106601#issuecomment-1170138123

Addresses https://github.com/flutter/flutter/issues/106601