AndroidX migration requires change of major version

[rostyslavroshak]

Official documentation suggests following:

Make sure to increment the major version of your plugin for this change and clearly document it in your plugin’s changelog. This breaking change requires manual migration for users to fix. Pub treats digits differently depending on whether a plugin is pre- or post-1.0.0. The very first digit is the major version for plugins that are at or above 1.0.0. For plugins below 1.0.0, the middle digit is considered to the major version.

It was a breaking change for us, because of usage another plugin that uses old support library.
So just letting you know, that some users might have same problems as well, because of unexpected migration to AndroidX.

[adammesa]

Judging by someone else's recent issue, I agree with this @charafau

[charafau]

Thanks for issue.

At the moment all I can do now is to add big text in readme that from 0.3.5 we use androidX..

[ly827]

Thanks for issue.

At the moment all I can do now is to add big text in readme that from 0.3.5 we use androidX..

Task :app:mergeDebugResources FAILED
:app:mergeDebugResources (Thread[Execution worker for ':' Thread 2,5,main]) completed. Took 0.004 secs.
*********************************************************
WARNING: This version of flutter_webview_plugin will break your Android build if it or its dependencies aren't compatible with AndroidX.
See https://goo.gl/CP92wY for more information on the problem and how to fix it.
This warning prints for all Android build failures. The real root cause of the error may be unrelated.
*********************************************************
63 actionable tasks: 62 executed, 1 up-to-date