-
Notifications
You must be signed in to change notification settings - Fork 1
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
Type 'Null' is not a subtype of type 'RenderBox' in type cast. #1
Comments
Thanks for reporting this issue. It seems that the RenderBox being null is an extremely rare situation, which is why there is no exception handling for it. Even in the latest version, this issue could still occur, so it’s important to address it. However, it would be greatly helpful if you could provide an example code where this exception happens for more accurate testing. 😀 |
Try updating to version 2.2.2 to see if the issue is resolved. (Since the structure differs from version 1.0, you may need to modify your existing code.) |
@MTtankkeo , thanks for update, I had updated the version. Lets see after release. |
@MTtankkeo , |
@MTtankkeo, I got one more crash related to this, on android device. Even this is related to other dependency (animated_list_plus) but, it might be helpful in providing you more detail. Fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: Null check operator used on a null value. Error thrown . |
Thanks, It appears that the related reorderable list package may be dynamically moving items or changing widget tree positions, which is causing unexpected exceptions related to the AnimationController. I believe I can address this by implementing additional exception handling to resolve the issue. i will soon release version 2.2.3 with a fix or improvement for this issue. |
@jitender-skycap A version 2.2.3 has been released to address this issue. Please update to the latest version and check if the exception still occurs. |
Thanks, @MTtankkeo , will update the sdk and update you after releasing new app version. |
@MTtankkeo after updating to version 2.2.3, still getting the issue. |
Released fix version 2.2.32 on issues related to this. Try update it version. |
I had developed an app and use firebase crashlytics to that and logged with occurrence of crash.
The text was updated successfully, but these errors were encountered: