@MarcusTomlinson I mis-read the code when I posted here - we're already looking in "~/snap/flutter/common/flutter". The issue is that we only do this if we find a file at /snap/flutter/current/flutter.sh:

Line 455 in 616ebc1

if (isLinux && fs.existsSync(flutterSnapScript)) {

So is the file /snap/flutter/current/flutter.sh in a different place on Arch? If I understand correctly, we're using this simple as a check for "does the user have the Flutter snap installed?" so we know whether it's reasonable to run ~/snap/flutter/common/flutter if it looks like an uninitialised SDK so it'll pass the later checks.

I wonder how the Android studio extension finds/prioritises SDK path

In the issue you linked, the project was created with flutter create then opened. In VS Code the same should work - as we should read the .packages file and find the SDK that way. It doesn't help for projects that haven't had the packages restored already though (or in the case where the Snap hasn't been initialised fully).

We could also probably easily add ~/snap/flutter/common/flutter to the default locations we search for SDKs which would solve this issue if the Snap was initialised, but it wouldn't help the case where it's been installed and not initialised.

Flutter SDK installed using Snap is not located correctly on Arch Linux #2886

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions