Warnings after Flutter upgrade - Missing plugin for Linux and Windows

[JayMoliya33]

After upgrading Flutter, I'm encountering warnings related to the amplify_secure_storage package. The package is referencing non-existent default plugins for Linux and Windows:

• Package amplify_secure_storage:linux references amplify_secure_storage_dart:linux as the default plugin, but the package does not exist, or is not a plugin package.
• Package amplify_secure_storage:windows references amplify_secure_storage_dart:windows as the default plugin, but the package does not exist, or is not a plugin package.

I'm using the following Amplify packages:

• amplify_api: ^1.6.2
• amplify_auth_cognito: ^1.6.1
• amplify_core: ^1.6.2
• amplify_flutter: ^1.6.1
• amplify_storage_s3: ^1.6.1

Flutter version:
Flutter 3.27.0 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 8495dee1fd (6 days ago) • 2024-12-10 14:23:39 -0800
Engine • revision 83bacfc525
Tools • Dart 3.6.0 • DevTools 2.40.2

Could you please advise on the necessary steps to resolve this issue?

[tyllark]

Hello @JayMoliya33, could you please try upgrading your packages to the latest versions (2.5.1) and let us know if that resolved your issue. There was a Plugin endorsement issue that was fixed in PR #5208.

[HoveringGoat]

This isnt really a fix if we can't upgrade to amplify gen 2.

[dtodt]

Same problem here, we can't upgrade to amplify gen 2 either.

[tyllark]

Hello @HoveringGoat and @dtodt, the amplify_flutter package supports the configuration format that is generated from Gen 1 (AmplifyConfig) and Gen 2 (AmplifyOutputs). When you call Amplify.configure we attempt to parse both the Gen 1 and 2 json formats and convert to the Gen 2 format as necessary.

I understand upgrading the amplify_flutter from version 1.X.X to 2.5.0 may result in some breaking changes, but our intention is that amplify_flutter 2.5.0 should support both Gen 1 and Gen 2.

[dtodt]

@tyllark my main problem to migrate from gen 1 is in fact dependency conflict:

Because every version of app from path depends on file_picker ^8.1.6 which depends on web ^1.0.0, every version of app from path requires web
  ^1.0.0.
And because amplify_analytics_pinpoint_dart >=0.4.3 depends on drift >=2.18.0 <2.19.0 which depends on web ^0.5.0, app from path is incompatible with
  amplify_analytics_pinpoint_dart >=0.4.3.

So I need to wait some update in amplify_analytics_pinpoint_dart upgrading its drift version and in amplify_analytics_pinpoint to upgrade amplify_analytics_pinpoint_dart.

I think that drift >=2.18.0 <2.24.0 would work well.

So either one of these options:

• wait until amplify dependency gets upgraded;
• replace file_picker by another package that does not depends on web 1.0.0.