Skip to content

[CP] handle FileSystemExtension during plugin symlinking across windows drives #136680

@christopherfujino

Description

@christopherfujino

Issue Link

#66224

Commit Hash

9751fe6

Target

beta

PR Link

#136681

Changelog Description

Handle file system exceptions when symlinking across Windows file system drives with user-friendly message.

Impacted Users

Flutter developers on windows machines with their Flutter SDK installed on one drive and their app on another

Impact Description

If you try to run/build a Flutter app on one windows drive while your Flutter SDK is installed on another, the tool will crash while trying to symlink native directories the latter to the former with a cryptic error message (see #66224).

Workaround

Whether we CP this or not, the workaround is the same: move your flutter project to the same drive as your Flutter SDK.

This CP will instruct the user about the workaround, however.

Risk

low

Test Coverage

yes

Validation Steps

On a Windows machine, create and build a flutter project on a different drive than that your Flutter SDK is installed in.

Metadata

Metadata

Labels

cp: approvedApproved cherry-pick requestcp: merge-to-betaCherry-picks that should be merged to betacp: mergedCherry-pick has been merged to the release branch.cp: reviewCherry-picks in the review queue

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions