Both changes have landed to Flutter stable so could this issue be resolved now?

I think I just found a bug related to the current implementation of Dart plugin registrants. PathProviderWindows's registerWith method is not properly called when the app code is running on non-root (secondary) isolates.

How to reproduce:

Create a Windows Flutter app that depends on path_provider.
Set the path_provider_windows version to the latest.
```
dependencies:
  path_provider_windows: ^2.0.3
```
Remove lines related to _manualDartRegistrationNeeded from your local path_provider source code.
In the app code, create an isolate that computes some platform-specific paths. For example,
```
Future<void> printPaths([var message]) async {
  final temporaryDirectory = await getTemporaryDirectory();
  print(temporaryDirectory.path);
}

printPaths().then((_) => compute(printPaths, null));
```
In this code, printPaths() will succeed but compute(printPaths, null) will throw an exception because the PathProviderPlatform instance automatically falls back to MethodChannelPathProvider which is not implemented for Windows.

The problem is that generated_main.dart's _PluginRegistrant.register is not called when a secondary isolate is spawned by the engine. Is this an expected behavior?

Remove manual platform registration in plugins #81421

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions