Status Update
Comments
du...@google.com <du...@google.com> #2
Same issue.
Try this:
Roll back to AS-C3.
Set gradle back to '...:3.6.0-alpha03'. (The issue is caused by this, I think.)
Clean project.
I'm sure an update will fix it.
Try this:
Roll back to AS-C3.
Set gradle back to '...:3.6.0-alpha03'. (The issue is caused by this, I think.)
Clean project.
I'm sure an update will fix it.
ro...@gmail.com <ro...@gmail.com> #3
Same issue.
du...@google.com <du...@google.com> #4
Successfully downgraded projects to use AS3.6C3
RG
RG
ro...@gmail.com <ro...@gmail.com> #5
Same issue here, downgrading to AS3.6C3 works OK
ro...@gmail.com <ro...@gmail.com> #6
New project does not produce this kind of error, will try to drill down to what dependency will break it.
sm...@gmail.com <sm...@gmail.com> #7
Have drilled down and found that the error occures on
dependencies {
...
implementation 'androidx.constraintlayout:constraintlayout:2.0.0-beta2'
...
}
tested with following alphas and betas
"alpha3": OK
"alpha4": Fail
"alpha5": Fail
"beta1": Fail
"beta2": Fail
This was a simple test, have not tested thoroughly with a more complex test yet.
-> Solution : Downgrade 'androidx.constraintlayout:constraintlayout:2.0.0-xxx' to 'androidx.constraintlayout:constraintlayout:2.0.0-alpha3'
RG
dependencies {
...
implementation 'androidx.constraintlayout:constraintlayout:2.0.0-beta2'
...
}
tested with following alphas and betas
"alpha3": OK
"alpha4": Fail
"alpha5": Fail
"beta1": Fail
"beta2": Fail
This was a simple test, have not tested thoroughly with a more complex test yet.
-> Solution : Downgrade 'androidx.constraintlayout:constraintlayout:2.0.0-xxx' to 'androidx.constraintlayout:constraintlayout:2.0.0-alpha3'
RG
Description
Component used: Paging 3 Version used: 'androidx.paging:paging-runtime-ktx:3.0.0-alpha02' Devices/Android versions reproduced on: Emulator / Device: Samsung S9 w/Q
If this is a bug in the library, we would appreciate if you could attach:
Referencing to: https://issuetracker.google.com/160192222 #12:
It seems that the LoadType.PREPEND requests are legitimate, but there are subsequent LoadType.APPEND reoccurring (with same PID) when load suspends (IE room database query with "withTransaction") on the first LoadType.APPEND. Shouldn't load wait for the returning MediatorResult before calling load again (Look for my arrows to the right in table below)?
Here's my new implementation for the RemoteMediator:
If I have time, I will give you a working proof-of-concept of the issue.
RG