Fixed
Status Update
Comments
du...@google.com <du...@google.com> #2
See
du...@google.com <du...@google.com>
ta...@gmail.com <ta...@gmail.com> #3
How are you enqueuing the work? Please provide a sample app that reproduces this problem.
ap...@google.com <ap...@google.com> #4
Check in Moto e3 Power / Andorid 6.0 Marshmallow
Sometimes Periodic workManager gets called two times.
If Periodic workManager gets called only one time than you have to uninstall the app and then install again to check Periodicworker called two times on Login button click.
Sometimes Periodic workManager gets called two times.
If Periodic workManager gets called only one time than you have to uninstall the app and then install again to check Periodicworker called two times on Login button click.
Description
Version used: 3.0.0-alpha08 or 3.0.0-alpha09
Devices/Android versions reproduced on: Samsung Galaxy S8 / Android 9
Starting with version 3.0.0-alpha08 of the Paging library, the MediatorResult.Success(false) value returned from a RemoteMediator.load(LoadType.REFRESH, state) call doesn’t trigger a RemoteMediator.load(LoadType.APPEND, state) call and doesn’t update PagingDataAdapter.loadStateFlow to notify that the refresh state has changed from LoadState.Loading to LoadState.NotLoading.
This bug can be reproduced by means of the following project, if you’ve changed the version of the Paging library it uses so that it’s equal to 3.0.0-alpha08 or 3.0.0-alpha09: