Crash in androidx.work.lint.InvalidPeriodicWorkRequestIntervalDetector [156823036]

Duplicate

of 152606442

Bug

Status Update

No update yet.

Description

ri...@soundcloud.com

created issue #1

May 17, 2020 10:29AM

AGP 3.6.3/4.0.0-rc01

WM: 2.3.4

stacktrace:

kotlin.TypeCastException: null cannot be cast to non-null type kotlin.Long
    at androidx.work.lint.InvalidPeriodicWorkRequestIntervalDetector.visitConstructor(InvalidPeriodicWorkRequestIntervalDetector.kt:70)
    at com.android.tools.lint.client.api.UElementVisitor$DelegatingPsiVisitor.visitNewExpression(UElementVisitor.kt:1100)
    at com.android.tools.lint.client.api.UElementVisitor$DelegatingPsiVisitor.visitCallExpression(UElementVisitor.kt:1064)
    at org.jetbrains.uast.kotlin.KotlinUFunctionCallExpression.accept(KotlinUFunctionCallExpression.kt:205)
    at org.jetbrains.uast.UQualifiedReferenceExpression$DefaultImpls.accept(UQualifiedReferenceExpression.kt:34)
    at org.jetbrains.uast.kotlin.KotlinUQualifiedReferenceExpression.accept(KotlinUQualifiedReferenceExpression.kt:27)
    at org.jetbrains.uast.UQualifiedReferenceExpression$DefaultImpls.accept(UQualifiedReferenceExpression.kt:33)
//omitted

I'm happy to share with you the class where it crashes. What the best way to do that?

Comments

ra...@google.com <ra...@google.com> #2May 18, 2020 04:18PM

Status: Duplicate of

152606442

Related bug -

https://issuetracker.google.com/issues/124511903

Initial loads in LimitOffsetPagingSource run in transaction but subsequent loads do not because of cost of transaction. Loads rely on count query to return correct LoadResult.

If count query is outdated, i.e. large amount of data deleted, LimitOffsetPagingSource can return i.e. empty/wrong data and incorrect itemsBefore/itemsAfter/prevKey/nextKey. This can happen if outdated PagingSource doesn't get invalidated in time.

Issue 156823036

Description

Issue summary

Comments

ra...@google.com <ra...@google.com> #2May 18, 2020 04:18PM

Add comment

Issue metadata