-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Compiler crash: Iterables do not have same length. #48148
Comments
Can i get the whole project if possible? |
I guess the problem is in the abstraction of classes they are not properly extended . |
The given example is self-contained and reproduces the crash. It isn't necessary to add a main function, just paste the example into an example.dart file and try to run it with |
okay , thank you I will try that. |
@modulovalue, I'm working on a fix. Your repo is sufficient. Thanks. |
hey can you help me understand what was the issu actually and how it was solved ? It seems hard to read from above given commit. |
The problem was caused by how the compiler builds the AST internally: We compile the AST in two phases. The first (outline phase) builds the library scopes with for instance field and method declarations with their declared types. The second (body phase) builds the initializers of field declarations and bodies of method declarations. Because of modular compilation (used for instance for the web development compiler) some parts of the body phase work must be performed during the outline phase. Amongst these is building the initializer of constant fields, like In the latter, the duplicate ASTs are generally discarded, but in this case, the constructor invocation for |
Thank you so much for your info. |
I see the same issue occur on Dart 3.2.0 (build 3.2.0-65.0.dev) (with Flutter) while debugging when trying to read a value by hovering over a property in IDEA.
|
Is there any solution for that? (Flutter 3.13) EDITED: |
same here, after trying to evaluate a dio response. Increasing sdk boundaries dont seem to have any effect
doctor:
|
@burekas7 @Craftplacer @Lonyless I think you should consider opening a new issue. |
@Lonyless |
@burekas7 @Craftplacer @Lonyless The stack traces are different enough to indicate that this is a new problem, so do create a new issue. Also, if you can create a repro it would be of much help. |
In my case it's happening even with |
same error after upgrading to flutter 3.13 in same use case like u... |
Same, happening exact after the responce of an api using dio. |
same here after upgrading flutter 3.13.3, dart 3.1.1 |
unchecking the unhandled exception in vs code works for me but i think this isn't the solution bcz we need to track unhandled exceptions. |
The issue has been fixed (see #53453) and is available in the current dev release and will be available in the next beta and stable releases. |
Same issue is happening with me when I am trying to debug the repsonse of an API. Unhandled exception: #17 IncrementalCompiler.compileExpression (package:front_end/src/fasta/incremental_compiler.dart:1853:12) the Dart compiler exited unexpectedly. flutter doctor output: |
Yes i have faced same error after upgrading Flutter version Note:- this issue is only faced when the variables is defined and want to check the its properties value then and then this error comes and stops the application and Before updating the environment it shows for defined variable also. |
The fix was first included in 3.2.0-154.0.dev so it has not yet been picked up by the current Flutter version. @christopherfujino Do you know when this can be expected to be picked up by Flutter? |
Not sure when exactly it rolled, but currently the engine is past that version, at 3.3.0-2.0.dev: flutter/engine@429a242 And at the Flutter SDK master channel HEAD, I see:
|
Ohmg I face this issue too when I am trying to debug the repsonse of an API.
|
@christopherfujino I am also facing this issue while fetching data from hive. |
Same issue, but I upgrade my flutter solved.
|
How did you go around it please? |
The text was updated successfully, but these errors were encountered: