The non-abstract class 'InputConnectionController' is missing implementations for these members: - TextInputClient.currentTextEditingValue

[masewo]

Steps to Reproduce

Building of my application not possible anymore while using zefyr 0.8.0 and flutter channel master (v1.13.3-pre.60) because of InputConnectionController not implementing currentTextEditingValue.

Fixed by implementing currentTextEditingValue in InputConnectionController:

masewo@2e37998

[xalabax]

Yes, it works for me. Thanks @masewo

zefyr:
git:
url: git://github.com/masewo/zefyr.git
path: packages/zefyr/
commit: 2e37998

[zakiso]

same issue

[mattheuten]

This is still an issue in the most recent version! Maybe try implementing the fix and releasing a new version?

[pulyaevskiy]

This keeps coming up with people using Flutter master or dev channels.

Note that Zefyr currently only supports stable versions of Flutter. Moreover published versions of this package will always target Flutter stable only.

We could potentially have some sort of -dev version published that covers changes from Flutter master but I’m not sure if it’s worth extra effort.

I’d like to have some sort of support for this scenario though. Current thinking is to make Zefyr master branch track Flutter master.

This has a downside of tying Zefyr release cycle to Flutter and forcing users of stable channel to switch to master to get latest fixes.

Note that if we use this strategy there will be no pub releases for changes in master so people using this version will have to use git repo dependency in their pubspec.

This is somewhat similar to discussion in #205 and @TimWhiting suggestion.

[sgehrman]

same issue.

[winwisely99]

I am running on the MASTER channel of Flutter.

The code changes i made:

master...winwisely99:master

What does not work:

• in Flutter Web, when going into edit mode you can type. In mobile and desktop it works fine.

---

Then i tried running on the STABLE channel.

But it was impossible to run Flutter web.

flutter config --enable-web
Setting "enable-web" value to "true".

You may need to restart any open editors for them to read new settings.
cd /Users/apple/workspace/go/src/github.com/winwisely99/zefyr/packages/zefyr/example && flutter run -d chrome
No devices found with name or id matching 'chrome'

You need to be on BETA channel in order to run Flutter Web:
https://flutter.dev/docs/get-started/web#set-up

---

So, then i tried running on the BETA channel.

Everything worked pretty much !!

SO, i was wondering if we can flip over to flutter beta channel so that we can get Flutter Web nice and stable ?

[winwisely99]

DEV channel works better actually.

[marcinOz]

Hi @winwisely99, what version of the flutter are you using as I checked on beta and dev, and on both without luck. With error:

Launching lib/main.dart on Chrome in debug mode...
Building application for the web...
Error creating leader|lib/main.ddc.dill
Error creating kernel summary for module:leader|lib/main.ddc.dill

Response:--dart-sdk-summary=file:///Users/StudioProjects/flutter/bin/cache/flutter_web_sdk/kernel/flutter_ddc_sdk.dill
...
Error compiling dartdevc module:zefyr|lib/src/widgets/buttons.ddc.js

packages/zefyr/src/widgets/input.dart:11:7: Error: The non-abstract class 'InputConnectionController' is missing implementations for these members:
 - TextInputClient.currentTextEditingValue
Try to either
 - provide an implementation,
 - inherit an implementation from a superclass or mixin,
 - mark the class as abstract, or
 - provide a 'noSuchMethod' implementation.

class InputConnectionController implements TextInputClient {
      ^^^^^^^^^^^^^^^^^^^^^^^^^
packages/flutter/src/services/text_input.dart: Context: 'TextInputClient.currentTextEditingValue' is defined here.


Failed after 306ms
Finished with error: Failed to build application for the Web.

My version is:

Flutter 1.15.3 • channel dev • https://github.com/flutter/flutter.git
Framework • revision 67826bdce5 (3 weeks ago) • 2020-02-10 14:59:32 -0800
Engine • revision 6158f03ef5
Tools • Dart 2.8.0 (build 2.8.0-dev.8.0 514a8d4c84)

and

Flutter 1.14.6 • channel beta • https://github.com/flutter/flutter.git
Framework • revision fabeb2a16f (5 weeks ago) • 2020-01-28 07:56:51 -0800
Engine • revision c4229bfbba
Tools • Dart 2.8.0 (build 2.8.0-dev.5.0 fc3af737c7)

[winwisely99]

Using beta.

I forked it: github.com/winwisely99/zefyr.git

Just a slight change to make it work.

[marcinOz]

It works! Thank you @winwisely99 🙇

[rahul-dutt-sharma]

Anyone got this to work on macos target?

[TimWhiting]

@pulyaevskiy

Just some more ideas on the flutter channels and this package versioning

This keeps coming up with people using Flutter master or dev channels.

Note that Zefyr currently only supports stable versions of Flutter. Moreover published versions of this package will always target Flutter stable only.

We could potentially have some sort of -dev version published that covers changes from Flutter master but I’m not sure if it’s worth extra effort.

I’d like to have some sort of support for this scenario though. Current thinking is to make Zefyr master branch track Flutter master.

This has a downside of tying Zefyr release cycle to Flutter and forcing users of stable channel to switch to master to get latest fixes.

They wouldn't necessarily have to switch to master for latest fixes. They might be able to switch to a flutter beta or dev channel release that Zefyr master is compatible with.

I think Zefyr has greater problems with the flutter versioning issue than other libraries because it is tied closely to the implementation of flutter's text field etc. Hopefully after the refactors to enable web and desktop there shouldn't be as many breaking changes as far as the text field's api in flutter.

It might just require some documentation in Zefyr master's CHANGELOG.md on which flutter version/s the Zefyr version is compatible / tested with. You could also specify the flutter version requirements in the pubspec.yaml's environment field. The latter solution would enforce the flutter version requirements and be a possible explanation to the users of the package rather than having duplicate issues for the same reason because of breaking changes in flutter master.

Note that if we use this strategy there will be no pub releases for changes in master so people using this version will have to use git repo dependency in their pubspec.

Or if Zefyr master tracks Flutter master than you could publish -dev versions as suggested. It seems like that is what the pub package publishing guidelines recommends for packages that depend on flutter versions: