EdsonBueno / infinite_scroll_pagination

Flutter package to help you lazily load and display pages of items as the user scrolls down your screen.
https://pub.dev/packages/infinite_scroll_pagination
MIT License
623 stars 210 forks source link

Null check operator used on a null value. Error thrown null. #225

Closed Andrushka1012 closed 1 year ago

Andrushka1012 commented 1 year ago

I got in my crashlitic issue Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError Null check operator used on a null value. Error thrown null.

Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: Null check operator used on a null value. Error thrown null. at PagingController.notifyStatusListeners(paging_controller.dart:170) at PagingController.value=(paging_controller.dart:94) at PagingController.appendPage(paging_controller.dart:105) at PagingController.appendLastPage(paging_controller.dart:114

Looks like _statusListeners is null and line if (_statusListeners!.isEmpty) { throw exception

ThomasCarrillo commented 1 year ago

Hi,

I got the same issue in my crashlytics :

Null check operator used on a null value. Error thrown null.
       at PagingController.notifyStatusListeners(paging_controller.dart:170)
       at PagingController.value=(paging_controller.dart:94)
       at PagingController.error=(paging_controller.dart:69)

My non-crash rate is decreasing like a rocket because of this, can you please take a look ?

Thank you in advance 😃

AmirMohammadKargar commented 1 year ago

Hi, I got in my sentry issue

Null check operator used on a null value

paging_controller.dart in PagingController.notifyStatusListeners at line 170 within infinite_scroll_pagination
paging_controller.dart in PagingController.value= at line 94 within infinite_scroll_pagination
paging_controller.dart in PagingController.appendPage at line 105 within infinite_scroll_pagination
paging_controller.dart in PagingController.appendLastPage at line 114 within infinite_scroll_pagination

can you please take a look ?

EdsonBueno commented 1 year ago

This is fixed by this PR and will be published in our next release.