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

getting PlatformException(channel-error, Unable to establish connection on channel: "dev.flutter.pigeon.wakelock_plus_platform_interface.WakelockPlusApi.toggle"., null, null) error when running test cases #67

Open
shivamtiwari-ttn opened this issue Jul 11, 2024 · 7 comments

Comments

@shivamtiwari-ttn
Copy link

I am using wakelock_plus for one of my classes to keep player screen on. Test cases related to that file are failing. I was earlier using wakelock, recently updated to wakelock_plus. In the test case file I have a setupAll method where earlier for wakelock 'wakelock_macos' was used for MethodChannel name like below.

const channel = MethodChannel('wakelock_macos');
TestDefaultBinaryMessengerBinding.instance.defaultBinaryMessenger
        .setMockMethodCallHandler(channel, (MethodCall methodCall) async {
      return null;
    });

for this test cases were passed successfully.

After comparing the wakelock and wakelock_plus libraries, I attempted to utilise the MethodChannel named 'wakelock_plus_macos' for wakelock_plus in the same way that we used it for wakelock.
const channel = MethodChannel('wakelock_plus_macos');

But test cases are failing with below error:
PlatformException(channel-error, Unable to establish connection on channel: "dev.flutter.pigeon.wakelock_plus_platform_interface.WakelockPlusApi.toggle"., null, null)

Now if I use 'dev.flutter.pigeon.wakelock_plus_platform_interface.WakelockPlusApi.toggle' as the MethodChannel name like
const channel = MethodChannel('dev.flutter.pigeon.wakelock_plus_platform_interface.WakelockPlusApi.toggle');

I am getting another error:

FormatException: Message corrupted

package:flutter/src/services/message_codecs.dart 532:16                               StandardMessageCodec.readValueOfType
package:flutter/src/services/message_codecs.dart 477:12                               StandardMessageCodec.readValue
package:flutter/src/services/message_codecs.dart 522:23                               StandardMessageCodec.readValueOfType
package:flutter/src/services/message_codecs.dart 477:12                               StandardMessageCodec.readValue
package:flutter/src/services/message_codecs.dart 609:41                               StandardMethodCodec.decodeMethodCall
package:flutter_test/src/test_default_binary_messenger.dart 300:45                    TestDefaultBinaryMessenger.setMockMethodCallHandler.<fn>
package:flutter_test/src/test_default_binary_messenger.dart 143:29                    TestDefaultBinaryMessenger.send
package:flutter/src/services/platform_channel.dart 218:54                             BasicMessageChannel.send
package:wakelock_plus_platform_interface/messages.g.dart 122:32                       WakelockPlusApi.toggle
package:wakelock_plus_platform_interface/src/method_channel_wakelock_plus.dart 20:16  MethodChannelWakelockPlus.toggle
package:wakelock_plus/wakelock_plus.dart 71:41                                        WakelockPlus.toggle

What should be used for MethodChannel to run test cases successfully

@shivamtiwari-ttn
Copy link
Author

For those who are facing such issue, I was able to pass the test cases by making below change in my test file.

I have replaced

const channel = MethodChannel('wakelock_macos');
TestDefaultBinaryMessengerBinding.instance.defaultBinaryMessenger
        .setMockMethodCallHandler(channel, (MethodCall methodCall) async {
      return null;
    });

to

TestDefaultBinaryMessengerBinding.instance.defaultBinaryMessenger
        .setMockMessageHandler(
            'dev.flutter.pigeon.wakelock_plus_platform_interface.WakelockPlusApi.toggle',
            (obj) async => obj);

@luckyhandler
Copy link

I face this error also when using the plugin in production. I'm using wakelock_plus: 1.1.4

@BolisettySujith
Copy link

@luckyhandler @shivamtiwari-ttn is there any fix for it ?

@MichaelDarkMostIo
Copy link

@diegotori Most likely related to Flutter upgrade (3.24.X)

@luckyhandler Have you upgraded Flutter version recently?

@diegotori
Copy link
Collaborator

@shivamtiwari-ttn please upgrade your wakelock_plus version to the latest 1.2.x version.

The latest ones are guaranteed to be compatible with Flutter 3.19 and higher.

When upgrading, also run flutter pub upgrade so that it pulls in the latest transitive dependencies that this library uses.

@MichaelDarkMostIo
Copy link

MichaelDarkMostIo commented Sep 27, 2024

Thanks @diegotori, we will try to upgrade versions.

So, it be caused because of mismatch in versions between platform interface and the package itself, right?

pubspec.lock

  wakelock_plus:
    dependency: "direct main"
    description:
      name: wakelock_plus
      sha256: f268ca2116db22e57577fb99d52515a24bdc1d570f12ac18bb762361d43b043d
      url: "https://pub.dev"
    source: hosted
    version: "1.1.4"
  wakelock_plus_platform_interface:
    dependency: transitive
    description:
      name: wakelock_plus_platform_interface
      sha256: "422d1cdbb448079a8a62a5a770b69baa489f8f7ca21aef47800c726d404f9d16"
      url: "https://pub.dev"
    source: hosted
    version: "1.2.1"

@diegotori
Copy link
Collaborator

Thanks @diegotori, we will try to upgrade versions.

So, it be caused because of mismatch in versions between platform interface and the package itself, right?

pubspec.lock

  wakelock_plus:
    dependency: "direct main"
    description:
      name: wakelock_plus
      sha256: f268ca2116db22e57577fb99d52515a24bdc1d570f12ac18bb762361d43b043d
      url: "https://pub.dev"
    source: hosted
    version: "1.1.4"
  wakelock_plus_platform_interface:
    dependency: transitive
    description:
      name: wakelock_plus_platform_interface
      sha256: "422d1cdbb448079a8a62a5a770b69baa489f8f7ca21aef47800c726d404f9d16"
      url: "https://pub.dev"
    source: hosted
    version: "1.2.1"

Once you upgrade both, it should work itself out.

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

5 participants