Fixed
Status Update
No update yet.
Comments
ra...@google.com
Please switch to using 2.3.4. We fixed lint issues in that release.
db...@digitalfleet.com
I'm reporting the issue for version 2.3.4. I see this lint error in version 2.3.4
ra...@google.com
Sorry, you can @SuppressLint for now. This looks like a bug in the lint rule.
db...@digitalfleet.com
Sample Repository that reproduces the issue,
https://github.com/dbriggsDFleet/WorkManagerLintBug/
1. checkout the sample repo.
2. run `./gradlew lintDebug`
3. Observer bug.
4. Observe build.gradle workmanager version 2.3.4
Maybe I'm missing something?
EDIT: Just saw your comment, glad we are on the same page. We are going to wait on updating instead of suppressing the lint check.
Thanks for looking at it!
1. checkout the sample repo.
2. run `./gradlew lintDebug`
3. Observer bug.
4. Observe build.gradle workmanager version 2.3.4
Maybe I'm missing something?
EDIT: Just saw your comment, glad we are on the same page. We are going to wait on updating instead of suppressing the lint check.
Thanks for looking at it!
ra...@google.com
Actually you should switch to 2.3.4. On 2.3.3 none of our lint rules get picked up by Studio because we not have the right metadata. So you lose all lint checks.
@SuppressLint is what you should do for now, to take advantage of the other checks.
ra...@google.com
The fix will go out as part of 2.4.0-alpha02.
Description
Version used: 2.3.4
Devices/Android versions reproduced on: Android Studio
On the latest version getting the following lint error this issue does not occur on 2.3.3. All of my periodic jobs intervals are at least 30 minutes.
lint-results-debug.xml
```
<issue
id="LintError"
severity="Error"
message="Unexpected failure during lint analysis of MyWorkManagerWrapper.java (this is a bug in lint or one of the libraries it depends on)

Message: null cannot be cast to non-null type kotlin.Long

The crash seems to involve the detector `androidx.work.lint.InvalidPeriodicWorkRequestIntervalDetector`.
You can try disabling it with something like this:
 android {
 lintOptions {
 disable "InvalidPeriodicWorkRequestInterval"
 }
 }

Stack: `TypeCastException:InvalidPeriodicWorkRequestIntervalDetector.visitConstructor(InvalidPeriodicWorkRequestIntervalDetector.kt:70)←UElementVisitor$DelegatingPsiVisitor.visitNewExpression(UElementVisitor.kt:1099)←UElementVisitor$DelegatingPsiVisitor.visitCallExpression(UElementVisitor.kt:1063)←UCallExpression$DefaultImpls.accept(UCallExpression.kt:99)←UCallExpressionEx$DefaultImpls.accept(UCallExpression.kt:-1)←JavaConstructorUCallExpression.accept(javaUCallExpressions.kt:123)←UQualifiedReferenceExpression$DefaultImpls.accept(UQualifiedReferenceExpression.kt:47)←JavaUCompositeQualifiedExpression.accept(JavaUCompositeQualifiedExpression.kt:23)`

You can set environment variable `LINT_PRINT_STACKTRACE=true` to dump a full stacktrace to stdout."
category="Lint"
priority="10"
summary="Lint Failure"
explanation="This issue type represents a problem running lint itself. Examples include failure to find bytecode for source files (which means certain detectors could not be run), parsing errors in lint configuration files, etc.

These errors are not errors in your own code, but they are shown to make it clear that some checks were not completed.">
<location
file="FILE_PATH/MyWorkManagerWrapper.java"/>
</issue>
```
Sample Code:
```
workRequest = new PeriodicWorkRequest.Builder(CustomWorker.class, workerType.interval, workerType.timeUnit).build();
workManager.enqueueUniquePeriodicWork(workerType.uniqueName, workerType.workPolicy, workRequest);
```
```
public enum PeriodicWorkerType {
PERIODIC_JOB("PERIODIC_JOB_V1", 30, TimeUnit.Minutes, ExistingPeriodicWorkPolicy.KEEP),
public final String uniqueName;
public final long interval;
public final TimeUnit timeUnit;
public final ExistingPeriodicWorkPolicy workPolicy;
PeriodicWorkerType(String uniqueName, long interval, TimeUnit timeUnit, ExistingPeriodicWorkPolicy workPolicy) {
this.uniqueName = uniqueName;
this.interval = interval;
this.timeUnit = timeUnit;
this.workPolicy = workPolicy;
}
}
```
If this is a bug in the library, we would appreciate if you could attach:
- Sample project to trigger the issue.
- A screenrecord or screenshots showing the issue (if UI related).