A KeyUpEvent is dispatched, but the state shows that the physical key is not pressed.

[shahzaibdev1]

Steps to reproduce

1. Use the following code for changing the route:

Navigator.pushReplacement(
          context,
          MaterialPageRoute(
            builder: (context) {
              return Builder(
                builder: (context) {
                  return TranslationDetails(text: lst, customPaint: _customPaint!, image: uiImage);
                },
              );
            },
          ),
        ).then((value) => _startLiveFeed);

2. Navigate to the TranslationDetails screen.
3. Press the back button (bottom/phone's native) to return to the previous screen.
4. Observe the error in the console.

Environment:

• Flutter version: 3.19.5
• Framework • revision 300451a (9 weeks ago) • 2024-03-27 21:54:07 -0500
• Engine • revision e76c956498
• Platform: Android
• Tools • Dart 3.3.3 • DevTools 2.31.1

Additional Information:

• No physical keyboard is attached to the device.
• The issue occurs with a 1-second delay/lag.

Expected results

The application should navigate between screens without any delay or error, regardless of the physical keyboard's status.

Actual results

════════ Exception caught by services library ══════════════════════════════════
A KeyUpEvent is dispatched, but the state shows that the physical key is not pressed. If this occurs in real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event model as documented in HardwareKeyboard. This was the event: KeyUpEvent#64ad8(physicalKey: PhysicalKeyboardKey#3b725(usbHidUsage: "0x1100000004", debugName: "Key with ID 0x1100000004"), logicalKey: LogicalKeyboardKey#5dfc4(keyId: "0x100001005", keyLabel: "Go Back", debugName: "Go Back"), character: null, timeStamp: 0:00:27.768097)
'package:flutter/src/services/hardware_keyboard.dart':
Failed assertion: line 509 pos 16: '_pressedKeys.containsKey(event.physicalKey)'
════════════════════════════════════════════════════════════════════════════════

Code sample

Code sample

Navigator.pushReplacement(
          context,
          MaterialPageRoute(
            builder: (context) {
              return Builder(
                builder: (context) {
                  return TranslationDetails(text: lst, customPaint: _customPaint!, image: uiImage);
                },
              );
            },
          ),
        ).then((value) => _startLiveFeed);

Screenshots or Video

No response

Logs

Logs

[Paste your logs here]

Flutter Doctor output

Doctor output

PS D:\translation_app> flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.19.5, on Microsoft Windows [Version 10.0.19045.4412], locale en-US)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.7.6)
[√] Android Studio (version 2022.3)
[√] VS Code (version 1.89.1)
[√] Connected device (6 available)
[√] Network resources

• No issues found!

[huycozy]

Hi @shahzaibdev1
For the issue to be workable, it needs to be reproducible with a completed and minimal reproducible code sample that doesn’t include 3rd party plugins or complex production code. Please provide such a sample, thank you.

[bsutton]

I'm seeing the same error on a linux desktop system (compile to linux desktop).

There is a keyboard attached.

AssertionError ('package:flutter/src/services/hardware_keyboard.dart': Failed assertion: line 509 pos 16: '_pressedKeys.containsKey(event.physicalKey)': A KeyUpEvent is dispatched, but the state shows that the physical key is not pressed. If this occurs in real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event model as documented in HardwareKeyboard. This was the event: KeyUpEvent#ac08a(physicalKey: PhysicalKeyboardKey#ae4f7(usbHidUsage: "0x00070016", debugName: "Key S"), logicalKey: LogicalKeyboardKey#45b63(keyId: "0x00000073", keyLabel: "S", debugName: "Key S"), character: null, timeStamp: 960:01:32.808000))

I'm getting the assert when I'm in a text field and occurs as soon as I start typing. The key is certainly being pressed when the error is generated.
It occurs on the down stroke (the error is throw whilst the key is press - I forced this by being slow to release the key).
I only see the error when I have the debugger set to show 'All Exceptions' - vs code.

If I disable the break on 'All Exceptions' the app behaves correctly.

Not exactly a small sample, but you can reproduce the problem with this app:
https://github.com/bsutton/handyman

launch the app, click the + button to add a Job.
Start typing in the Job Summary field.

bsutton@slayer4:~/git/handyman/handyman$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.22.0, on Ubuntu 22.04.4 LTS 6.5.0-28-generic, locale en_AU.UTF-8)
[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/linux#android-setup for more details.
[✓] Chrome - develop for the web
[✓] Linux toolchain - develop for Linux desktop
[!] Android Studio (version unknown)
    ✗ Unable to determine Android Studio version.
    ✗ android-studio-dir = /home/bsutton/Android/Sdk
    ✗ Unable to find bundled Java version.
[✓] VS Code (version 1.89.1)
[✓] Connected device (2 available)
[✓] Network resources

! Doctor found issues in 2 categories.

[huycozy]

@bsutton Your project is a complex one that is not easy for us to look at. Do you see the issue with a simple app having only a TextField? If so, can you share detailed steps by steps to reproduce it?

[github-actions]

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now.
If you find this problem please file a new issue with the same description, what happens, logs and the output of 'flutter doctor -v'. All system setups can be slightly different so it's always better to open new issues and reference the related ones.
Thanks for your contribution.

[github-actions]

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.