codegrue / flutter_material_pickers

A flutter package for displaying common picker dialogs.

Home Page:https://pub.dev/packages/flutter_material_pickers

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Use flutter_colorpicker latest version

armandojimenez opened this issue · comments

Can this be updated to use the latest version of flutter_colorpicker? I’m having this issue mchome/flutter_colorpicker#48 (comment) and it was resolved on the latest version

I'm getting a build error trying to use colorpicker 0.5.0. Trying to solve it.

Launching lib/main.dart on iPhone 12 Pro Max in debug mode...
lib/main.dart:1
Xcode build done.                                           61.8s
Failed to build iOS app
Error output from Xcode build:
↳
    ** BUILD FAILED **
Xcode's output:
↳
    ../../../../../../.pub-cache/hosted/pub.dartlang.org/flutter_colorpicker-0.5.0/lib/src/hsv_picker.dart:730:43: Error: The parameter 'event' of the method 'AlwaysWinPanGestureRecognizer.addAllowedPointer' has type 'PointerDownEvent', which does not match the corresponding type, 'PointerEvent', in the overridden method, 'DragGestureRecognizer.addAllowedPointer'.
     - 'PointerDownEvent' is from 'package:flutter/src/gestures/events.dart' ('../../../../../../Development/flutter/packages/flutter/lib/src/gestures/events.dart').
     - 'PointerEvent' is from 'package:flutter/src/gestures/events.dart' ('../../../../../../Development/flutter/packages/flutter/lib/src/gestures/events.dart').
    Change to a supertype of 'PointerEvent', or, for a covariant parameter, a subtype.
      void addAllowedPointer(PointerDownEvent event) {
                                              ^
    ../../../../../../Development/flutter/packages/flutter/lib/src/gestures/monodrag.dart:256:8: Context: This is the overridden method ('addAllowedPointer').
      void addAllowedPointer(PointerEvent event) {
           ^
    Command PhaseScriptExecution failed with a nonzero exit code
    note: Using new build system
    note: Building targets in parallel
    note: Planning build
    note: Analyzing workspace
    note: Constructing build description
    note: Build preparation complete
    /Users/jeff/OneDrive/Projects/Code/Flutter Packages/flutter_material_pickers/example/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.5.99. (in target 'SDWebImage' from project 'Pods')
    /Users/jeff/OneDrive/Projects/Code/Flutter Packages/flutter_material_pickers/example/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.5.99. (in target 'SwiftyGif' from project 'Pods')
    warning: Capabilities for Signing & Capabilities may not function correctly because its entitlements use a placeholder team ID. To resolve this, select a development team in the Runner editor. (in target 'Runner' from project 'Runner')
    /Users/jeff/OneDrive/Projects/Code/Flutter Packages/flutter_material_pickers/example/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.5.99. (in target 'Flutter' from project 'Pods')
Could not build the application for the simulator.
Error launching application on iPhone 12 Pro Max.
Exited (sigterm)

I think the problem is the breaking change is in dev channel, but the package was updated and now does not run on stable. I don't know if then this package has to wait until the breaking change hits stable :(

My preference is to deploy the package as the stable branch. How urgent is this change for you?

I'm planning to release next month, but no problem really, if the breaking change is not in stable by then, i will fork this repo and update the plugin version. I would like to release using stable, but the dev channel has the ios jank fix thing, and would like to release with the SkSL warmup working on iOS

Can this be updated but left on a pre-release dev version so it's ready when this breaking change hits?