IssueTracker

It seems the print is benign so I'll remove it; Could be worth it to find out how the message carrying information about "cb 0" (0 is not a valid color buffer handle) ever arrives to that line though

I agree with Sergey -- while I think it's fine to remove some logging messages that aren't necessary, the root problem here is that Studio shows everything emitted as if they are errors, with one notification bubble per message. We don't do that for other tools that Studio launches, and in particular, this isn't specific to the "cb 0" message I showed here; there were earlier (different) error messages during the boot as well.

This behavior was requested specifically by the emulator team (vharron@ iirc, so at least 3-4 years ago). Let me see if I have any more details on why this was requested.

I couldn't find any relevant threads. IIRC, the main concern at that time was that warnings at startup (e.g. missing acceleration) really needed to be bubbled up to the users. If that is not an issue anymore, and the emulator team only wants errors to be visible, then the proposed change SGTM.

comment#7:

To assist us in investigate this issue, could you please provide the following details:

1. Did the issue begin immediately after updating your AGP version, while keeping all other dependencies and configurations unchanged?
2. What was the previous AGP version you were using, and to which version did you update?
3. Did you update any other libraries or dependencies in your project besides the AGP?
4. If you haven't updated to the latest AGP version yet, have you tried doing so to see if the issue persists?

Hey Jinseong, do you know anything about this recent lent change?

A couple clarifications:

• It looks like it's not about release apk v.s. debug. Even ./gradlew :app:lintDebug failed locally, with the same error.
• Indeed, this is introduced between AGP 8.6.0-alpha01 and 8.6.0-alpha02, and present until 8.6.0-alpha05
• Since AGP 8.6.0-alpha06, I got the following instead:

Stack: NullPointerException:OpaqueUnitKeyDetector.isNullableAny(OpaqueUnitKeyDetector.kt:205)
←OpaqueUnitKeyDetector.visitMethodCall(OpaqueUnitKeyDetector.kt:76)
←UElementVisitor$DelegatingPsiVisitor.visitMethodCallExpression(UElementVisitor.kt:778)
←UElementVisitor$DelegatingPsiVisitor.visitCallExpression(UElementVisitor.kt:758)
←KotlinUFunctionCallExpression.accept(KotlinUFunctionCallExpression.kt:271)
←ImplementationUtilsKt.acceptList(implementationUtils.kt:15)
←UBlockExpression.accept(UBlockExpression.kt:21)
←ULambdaExpression.accept(ULambdaExpression.kt:40)
←ImplementationUtilsKt.acceptList(implementationUtils.kt:15)
←KotlinUFunctionCallExpression.accept(KotlinUFunctionCallExpression.kt:275)
←ImplementationUtilsKt.acceptList(implementationUtils.kt:15)
←UBlockExpression.accept(UBlockExpression.kt:21)←ULambdaExpression.accept(ULambdaExpression.kt:40)
←ImplementationUtilsKt.acceptList(implementationUtils.kt:15)
←KotlinUFunctionCallExpression.accept(KotlinUFunctionCallExpression.kt:275)
←UQualifiedReferenceExpression.accept(UQualifiedReferenceExpression.kt:34)
←ImplementationUtilsKt.acceptList(implementationUtils.kt:15)
←UBlockExpression.accept(UBlockExpression.kt:21)
←UMethod.accept(UMethod.kt:45)
←ImplementationUtilsKt.acceptList(implementationUtils.kt:15)
←AbstractKotlinUClass.accept(AbstractKotlinUClass.kt:213)
←ImplementationUtilsKt.acceptList(implementationUtils.kt:15)
←UFile.accept(UFile.kt:89)
←UastLintUtilsKt.acceptSourceFile(UastLintUtils.kt:936)
←UElementVisitor$visitFile$3.run(UElementVisitor.kt:212)
←LintClient.runReadAction(LintClient.kt:1781)
←LintDriver$LintClientWrapper.runReadAction(LintDriver.kt:2745)
←UElementVisitor.visitFile(UElementVisitor.kt:209)
←LintDriver$visitUastDetectors$1.run(LintDriver.kt:2046)
...

which is fixed at https://android-review.git.corp.google.com/q/I91da3fd0598d64f184fa56a5d1240c8d5335dca6, but unclear which version of androidx.compose.runtime will include that fix.

In comment#5, I noticed:

##### 'kotlin.experimental.tryK2' results #####
:app:compileReleaseKotlin: 2.0 language version
##### 100% (1/1) tasks have been compiled with Kotlin 2.0 #####

and I also saw locally:

w: The `kotlin.experimental.tryK2` deprecated property is used in your build.
Please, stop using it as it is unsupported and may apply no effect to your build.

Note that that flag is gone after LV 2.0, and renamed to tryNext: https://youtrack.jetbrains.com/issue/KT-61975/Re-purpose-kotlin.experimental.tryK2

But, this means you're using Kotlin LV 2.0, and we intentionally align Lint w/ K2 UAST when LV is 2.0. Thank you for early adapting new toolings!

Unfortunately(?), this means a bug in K2 UAST, and adding the following to gradle.properties will unblock you:

#kotlin.experimental.tryK2=true
...
android.lint.useK2Uast=false

For internal records,

Since AGP 8.6.0-alpha06, I got the following instead:

What's changed between 8.6.0-alpha05 and alpha06 is described at b/346451894#comment2 and b/346452850#comment2.

do you know anything about this recent lint change?

Indeed, this is introduced between AGP 8.6.0-alpha01 and 8.6.0-alpha02

Around May 15 cut, one major(?) change is to bump up Lint's kotlinc artifacts from 2.0.0-RC2 to 2.0.0-RC3.

But... perhaps this is working as intended. When I use Studio w/ K2 mode, MediatorLiveData#addSource's lambda parameter, data, is marked as List<OrderListEntity>?, whereas in K1 mode, it is List<OrderListEntity>!, indicating platform type. And, even before NullSafeMutableLiveData check in androidx.lifecycle reports an error, K2 IDE shows an error too (screenshot attached).

Another workaround is to specify the type, e.g.,

    init {
        _orders.addSource(getAllOrders()) { data: List<OrderListEntity> ->
            _orders.value = data
        }
    }

Could you please clarify — does Kotlin 2.0 comes with K2 compiler?

Yes: https://blog.jetbrains.com/kotlin/2023/02/k2-kotlin-2-0/

Re: comment#14,

do you know anything about this recent lint change?

Indeed, this is introduced between AGP 8.6.0-alpha01 and 8.6.0-alpha02

Around May 15 cut, one major(?) change is to bump up Lint's kotlinc artifacts from 2.0.0-RC2 to 2.0.0-RC3.

That RC2..RC3 is quite small window. I almost forgot: b/331429710 (Align LV2.0 with K2 Lint) is done at 8.6.0-alpha02.

Sorry for changing the component multiple times. :)

Finally, reproduced in Lifecycle lint's own test infra:

org.junit.ComparisonFailure: expected:<[No warnings.]> but was:<[src/Test.kt:8: Error: Expected non-nullable value [NullSafeMutableLiveData]
        myData.value = data
                       ~~~~
1 errors, 0 warnings]>
	at org.junit.Assert.assertEquals(Assert.java:117)
	at org.junit.Assert.assertEquals(Assert.java:146)
	at com.android.tools.lint.checks.infrastructure.TestLintResult.expect(TestLintResult.kt:123)
	at com.android.tools.lint.checks.infrastructure.TestLintResult.expect$default(TestLintResult.kt:96)
	at com.android.tools.lint.checks.infrastructure.TestLintResult.expectClean(TestLintResult.kt:252)
	at androidx.lifecycle.livedata.core.lint.NonNullableMutableLiveDataDetectorTest.lambdaParameterFromMediatorLiveData(NonNullableMutableLiveDataDetectorTest.kt:1076)

Ported to https://youtrack.jetbrains.com/issue/KTIJ-30464

Upstream fix landed: https://github.com/JetBrains/intellij-community/commit/f87c9af24d15d840aa55a7cdc7cf38c00f9adfec and will be in 2024.3

^ But, that doesn't mean we should wait for 243 merge into Studio (ETA: around the end of this year). I'm just waiting for 242 merge into Studio, and once it's done, I'll cherry-pick the fix such that this can be fixed in a month or two.

I accidentally left comments in a wrong tracker, like b/349411310#comment6:

I marked this fixed so that the bot can chime in and said which version contains the fix. I expect it to be 8.7.0-alpha04 (cut yesterday). Stay tuned; I have a repro project, so I'll try that myself as well.

I can confirm that, by upgrading gradle to 8.8 and AGP to 8.7.0-alpha04, task :app:lintDebug went well.