Skip to content
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

[BUG] #217

Open
ssoad opened this issue Dec 17, 2024 · 3 comments
Open

[BUG] #217

ssoad opened this issue Dec 17, 2024 · 3 comments

Comments

@ssoad
Copy link

ssoad commented Dec 17, 2024

Describe the bug
A clear and concise description of what the bug is.

When using Flutter 3.27.0, the quill_html_editor package references quill_html_editor:android and quill_html_editor:ios as the default plugins, but it does not provide an inline implementation. This causes build issues.

To Reproduce
Steps to reproduce the behavior:

  1. Update Flutter to version 3.27.0.
  2. Add the quill_html_editor package to your

pubspec.yaml

.
3. Run flutter pub get.
4. Attempt to build the project.
5. See warning.

Warning
The package should either avoid referencing a default implementation via platforms: android: default_package: quill_html_editor or add an inline implementation to quill_html_editor via platforms: android: pluginClass or dartPluginClass.

Desktop (please complete the following information):

  • OS: [e.g. macOS]
  • Browser [e.g. Chrome, Safari]
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, Safari]
  • Version [e.g. 22]

Flutter Doctor
Please run flutter doctor in the terminal and add the log here.

[✓] Flutter (Channel stable, 3.27.0, on macOS 12.3.1 21E258 darwin-x64, locale en-US)
    • Flutter version 3.27.0 at /Users/username/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 1234567890 (3 days ago), 2023-10-01 12:34:56 -0700
    • Engine revision abcdef1234
    • Dart version 2.17.0
    • DevTools version 2.12.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/username/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • ANDROID_HOME = /Users/username/Library/Android/sdk
    • Java binary at: /usr/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_292-b10)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] Connected device (3 available)
    • iPhone 12 (mobile) • 12345678-1234-1234-1234-123456789012 • ios • com.apple.CoreSimulator.SimRuntime.iOS-14-5 (simulator)
    • macOS (desktop)    • macos                                • darwin-x64     • macOS 12.3.1 21E258 darwin-x64
    • Chrome (web)       • chrome                               • web-javascript • Google Chrome 100.0.4896.127

• No issues found!
@gustavo-moreira-pinto
Copy link

After I upgraded for new Flutter version 3.27.X, I always receve this messages:

Package quill_html_editor_v2:android references quill_html_editor:android as the default plugin, but the package does not exist, or is not a plugin package.
Ask the maintainers of quill_html_editor_v2 to either avoid referencing a default implementation via platforms: android: default_package: quill_html_editor or create a plugin named quill_html_editor.

Package quill_html_editor_v2:ios references quill_html_editor:ios as the default plugin, but the package does not exist, or is not a plugin package.
Ask the maintainers of quill_html_editor_v2 to either avoid referencing a default implementation via platforms: ios: default_package: quill_html_editor or create a plugin named quill_html_editor.

Package quill_html_editor_v2:android references quill_html_editor:android as the default plugin, but the package does not exist, or is not a plugin package.
Ask the maintainers of quill_html_editor_v2 to either avoid referencing a default implementation via platforms: android: default_package: quill_html_editor or create a plugin named quill_html_editor.

Package quill_html_editor_v2:ios references quill_html_editor:ios as the default plugin, but the package does not exist, or is not a plugin package.
Ask the maintainers of quill_html_editor_v2 to either avoid referencing a default implementation via platforms: ios: default_package: quill_html_editor or create a plugin named quill_html_editor.

Package quill_html_editor_v2:android references quill_html_editor:android as the default plugin, but the package does not exist, or is not a plugin package.
Ask the maintainers of quill_html_editor_v2 to either avoid referencing a default implementation via platforms: android: default_package: quill_html_editor or create a plugin named quill_html_editor.

Package quill_html_editor_v2:ios references quill_html_editor:ios as the default plugin, but the package does not exist, or is not a plugin package.
Ask the maintainers of quill_html_editor_v2 to either avoid referencing a default implementation via platforms: ios: default_package: quill_html_editor or create a plugin named quill_html_editor.

For now I'm returning the flutter version to 3.24.5 using the flutter downgrade 3.24.5 command, but it is necessary that the error be corrected for it to work in the new versions of Flutter.

@gerken-tss
Copy link

@gustavo-moreira-pinto
Yes, same for me.

I am generally having a bad feeling about this package. Last update was 11 months ago and even bugs like these here are not being addressed. Maybe it's time to fork it or look for an alternative? Does somebody have one?

@ssoad
Copy link
Author

ssoad commented Dec 19, 2024

@gustavo-moreira-pinto Yes, same for me.

I am generally having a bad feeling about this package. Last update was 11 months ago and even bugs like these here are not being addressed. Maybe it's time to fork it or look for an alternative? Does somebody have one?

I'm trying to resolve the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants