[Bug] Comiple error after Flutter 3.19.0 upgrade

[roman423]

Error

/AppData/Local/Pub/Cache/hosted/pub.dev/pluto_grid-7.0.2/lib/src/manager/shortcut/pluto_grid_shortcut.dart(33,39): error GC2F972A8: The argument type 'RawKeyEvent' can't be assigned to the parameter type 'KeyEvent'. [\build\windows\x64\flutter\flutter_assemble.vcxproj]
*****/AppData/Local/Pub/Cache/hosted/pub.dev/pluto_grid-7.0.2/lib/src/manager/shortcut/pluto_grid_shortcut.dart(33,46): error GC2F972A8: The argument type 'RawKeyboard' can't be assigned to the parameter type 'HardwareKeyboard'. [***\build\windows\x64\flutter\flutter_assemble.vcxproj]

Environment

Flutter 3.19.0, on Microsoft Windows [Version 10.0.22631.3155], locale de-DE)
Dart version 3.3.0
PlutoGrid v7.0.2

[Yusufihsangorgel]

+++

[GayeKone222]

same problem. any solutions ?

[aymswick]

+++ and "me too" comments are noisy and unhelpful, just use the reactions button

This project is in a confusing state, to see what I mean please read this thread:
#968

The tl;dr is:

• Original author/maintainer has abandoned and nobody can write to this repo
• Someone forked it already and has started making changes (though they are essentially 1 person "doing their best") and partially released the functionality of the original package at pluto_grid_plus. Notably, the pluto_grid_export package has not been republished. I believe while they have not answered issues for a month, they have done prior work to migrate the changes represented by some PRs in this repo and they are moving in a positive direction, help is needed! As of yesterday, this particular bug is still present in pluto_grid_plus. There is discussion of opening up the fork to more maintainers.
• There is now a 3rd fork above which contains a replication of the fixes to the RawKeyEvent breaking change that someone put up a PR for months ago (though I don't know how anyone would discover this due to its nondescript name [FIX BUG ON WEB] [FIX BUG ON WEB] #979

Sorry there isn't an easier answer to your bug discovery, I'm just a guy in the same situation a couple days ahead of you; trying to spread the knowledge so we can all work in a single direction and not create more noise / future abandoned forks.

[ldsouza93]

me2

[kiskelover]

same problem

flutter 3.19

[jayakumarzoftsol]

Same problem . My app broke due to this. urgent help needed :)

[jayakumarzoftsol]

I have a fork of this repo and landed this fix on there. Not sure if everything is working fine as it should, but the code is running again.

Just use this in your pubspec:

pluto_grid:
  git: https://github.com/Macacoazul01/pluto_grid

No Its not working showing the dependancy issue with pluto_grid_export

[Macacoazul01]

Try the one @aymswick said, pluto_grid_plus

[pasaneramusugoda]

+++ and "me too" comments are noisy and unhelpful, just use the reactions button

This project is in a confusing state, to see what I mean please read this thread: #968

The tl;dr is:

• Original author/maintainer has abandoned and nobody can write to this repo
• Someone forked it already and has started making changes (though they are essentially 1 person "doing their best") and partially released the functionality of the original package at pluto_grid_plus. Notably, the pluto_grid_export package has not been republished. I believe while they have not answered issues for a month, they have done prior work to migrate the changes represented by some PRs in this repo and they are moving in a positive direction, help is needed! As of yesterday, this particular bug is still present in pluto_grid_plus. There is discussion of opening up the fork to more maintainers.
• There is now a 3rd fork above which contains a replication of the fixes to the RawKeyEvent breaking change that someone put up a PR for months ago (though I don't know how anyone would discover this due to its nondescript name [FIX BUG ON WEB] [FIX BUG ON WEB] #979

Sorry there isn't an easier answer to your bug discovery, I'm just a guy in the same situation a couple days ahead of you; trying to spread the knowledge so we can all work in a single direction and not create more noise / future abandoned forks.

doonfrs#4 (comment)

Seems pluto_grid_plus_export: ^1.0.4 is now available.

[ghost]

I have the same problem as mentioned, the solution was to return to Flutter version 3.16.8 on channel stable. I hope they can solve it soon, so I can continue working with this package.

[ecoant]

I have the same problem as mentioned, the solution was to return to Flutter version 3.16.8 on channel stable. I hope they can solve it soon, so I can continue working with this package.

buddy, nobody is going to solve it on this repository. All the info you need is present in the comments above. Switch to the pluto_grid_plus package. The fix is merged in there.

[dsyrstad]

• Original author/maintainer has abandoned and nobody can write to this repo

This is not true. pluto_grid 8.0.0 was released on 2024-03-01 which solves the issue with Flutter 3.19.x.

But for me, the problem is now pluto_grid_export is now incompatible with pluto_grid 8.0.0:

Because pluto_grid_export 1.0.6 depends on pluto_grid >=3.0.2 <8.0.0 and <app> depends on pluto_grid 8.0.0, pluto_grid_export 1.0.6 is forbidden.

[ecoant]

• Original author/maintainer has abandoned and nobody can write to this repo

This is not true. pluto_grid 8.0.0 was released on 2024-03-01 which solves the issue with Flutter 3.19.x.

But for me, the problem is now pluto_grid_export is now incompatible with pluto_grid 8.0.0:

Because pluto_grid_export 1.0.6 depends on pluto_grid >=3.0.2 <8.0.0 and <app> depends on pluto_grid 8.0.0, pluto_grid_export 1.0.6 is forbidden.

It absolutely was true at the time of my comment. It looks like the maintainer of this repo has returned to partially fix that error, but as you point out, you still won't get anywhere with export. I'm not sure what's going on here but you have an alternative option in pluto_grid_plus.

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 14 days since being marked as stale.