Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Flutter plugins don't work on windows - GeneratedPluginRegistrant #9953

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
DrasiusMajere opened this issue May 10, 2017 · 5 comments
Closed
Assignees
Labels
c: crash Stack traces logged to the console c: regression It was better in the past than it is now

Comments

@DrasiusMajere
Copy link

DrasiusMajere commented May 10, 2017

Steps to Reproduce

After upgrade flutter, now pathprovider is a plugin. I try to use it but get the below error. I think something is wrong with registration of plugins. The GeneratedPluginRegistrant file is generated automatically.
This is the output on a new project. Although in my old project fails too. Furthermore in my old app show an additional issue in the settings.gradle file that is not updated.

Logs

PS C:\PROGRAMACION\FLUTTER\mysterion> flutter run
Running 'flutter packages get' in mysterion...        1.2s
Launching lib/main.dart on SM A510F in debug mode...
Running 'gradle assembleDebug'...
C:\PROGRAMACION\FLUTTER\mysterion\android\app\src\main\java\io\flutter\plugins\GeneratedPluginRegistrant.java:11: error: cannot find symbol
    PathProviderPlugin.registerWith(registry.registrarFor("io.flutter.plugins.path_provider.PathProviderPlugin"));
                      ^
  symbol:   method registerWith(Registrar)
  location: class PathProviderPlugin
1 error

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
Gradle build failed: 1

Flutter Doctor

PS C:\PROGRAMACION\FLUTTER\mysterion> flutter doctor
[√] Flutter (on Microsoft Windows [Versión 10.0.15063], channel master)
    • Flutter at C:\flutter
    • Framework revision 9b56c1c58c (3 hours ago), 2017-05-10 09:41:55 +0200
    • Engine revision cbbf956fcb
    • Tools Dart version 1.23.0-dev.11.11

[√] Android toolchain - develop for Android devices (Android SDK 25.0.3)
    • Android SDK at C:\Users\Drasius\AppData\Local\Android\sdk
    • Platform android-25, build-tools 25.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version: OpenJDK Runtime Environment (build 1.8.0_112-release-b06)

[√] Android Studio (version 2.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Gradle version 3.2
    • Java version: OpenJDK Runtime Environment (build 1.8.0_112-release-b06)

[-] IntelliJ IDEA Community Edition (version 14)
    • Dart plugin version 141.1586
    • Flutter plugin not installed; this adds Flutter specific functionality.
    • For information about managing plugins, see
      https://www.jetbrains.com/help/idea/managing-plugins.html

[-] WebStorm (version 2016.1)
    • Flutter plugin not installed; this adds Flutter specific functionality.
    • For information about managing plugins, see
      https://www.jetbrains.com/help/idea/managing-plugins.html

[√] Connected devices
    • SM A510F • 3300886347c56327 • android-arm • Android 6.0.1 (API 23)

> For more information about diagnosing and reporting Flutter bugs, please see [https://flutter.io/bug-reports/](https://flutter.io/bug-reports/).
@mit-mit
Copy link
Member

mit-mit commented May 10, 2017

I'm really sorry, but this plugin is currently broken. @szakarias is working on fixing it, and a new version will be published shortly!

@mit-mit mit-mit added c: crash Stack traces logged to the console c: regression It was better in the past than it is now labels May 10, 2017
@DrasiusMajere
Copy link
Author

I test sharedpreferences plugin and the same error

@mit-mit
Copy link
Member

mit-mit commented May 10, 2017

Yes, all plugins need to be updated after this breaking change:
https://groups.google.com/forum/#!topic/flutter-dev/zba1Ynf2OKM

Also, we are working on adding test automation in travis to prevent breaks like this going undetected.

Sorry about the breaks once again, these were the last planned breaking changes to plugins.

@DrasiusMajere
Copy link
Author

thank you, sorry not needed it's normal in development. I like working with flutter and dart techs. keep going like this

@github-actions
Copy link

github-actions bot commented Sep 1, 2021

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
c: crash Stack traces logged to the console c: regression It was better in the past than it is now
Projects
None yet
Development

No branches or pull requests

3 participants