https://kotlinlang.org logo
#compose
Title
# compose
v

vide

11/17/2023, 12:23 PM
I'm trying to update to 1.6.0-beta01 and
./gradlew check
fails with an error message I don't really understand. 🧵
Copy code
Lint found an issue registry (androidx.compose.runtime.lint.RuntimeIssueRegistry)
which contains some references to invalid API:
org.jetbrains.kotlin.analysis.api.session.KtAnalysisSessionProvider: 
[...]
Copy code
> Task :app:lintDemoDebug FAILED
/home/runner/.gradle/caches/transforms-3/d23adda673b13392f4128346b11591b3/transformed/runtime-release/jars/lint.jar: Error: Library lint checks reference invalid APIs; these checks will be skipped!

Lint found an issue registry (androidx.compose.runtime.lint.RuntimeIssueRegistry)
which contains some references to invalid API:
org.jetbrains.kotlin.analysis.api.session.KtAnalysisSessionProvider: org.jetbrains.kotlin.analysis.api.lifetime.KtLifetimeTokenFactory getTokenFactory()
(Referenced from androidx/compose/runtime/lint/AutoboxingStateCreationDetector.class)

Therefore, this lint check library is not included
in analysis. This affects the following lint checks:
AutoboxingStateValueProperty
AutoboxingStateCreation
CoroutineCreationDuringComposition
FlowOperatorInvokedInComposition
ComposableLambdaParameterNaming
ComposableLambdaParameterPosition
ComposableNaming
StateFlowValueCalledInComposition
CompositionLocalNaming
MutableCollectionMutableState
ProduceStateDoesNotAssignValue
RememberReturnType
OpaqueUnitKey
UnrememberedMutableState

To use this lint check, upgrade to a more recent version
of the library. [ObsoleteLintCustomCheck]

   Explanation for issues of type "ObsoleteLintCustomCheck":
   Lint can be extended with "custom checks": additional checks implemented by
   developers and libraries to for example enforce specific API usages
   required by a library or a company coding style guideline.

   The Lint APIs are not yet stable, so these checks may either cause a
   performance degradation, or stop working, or provide wrong results.

   This warning flags custom lint checks that are found to be using obsolete
   APIs and will need to be updated to run in the current lint environment.

   It may also flag issues found to be using a newer version of the API,
   meaning that you need to use a newer version of lint (or Android Studio or
   Gradle plugin etc) to work with these checks.
Does this mean I would have to upgrade to • Android Gradle Plugin 8.3.0-alpha09 which requires ◦ Android Studio Iguana | 2023.2.1 Canary 9Gradle 8.4 for the check in 1.6.0-beta01 to pass or am I missing something here? blob thinking fast
Bumping this thread because running lint/check on 1.6.0-beta01 still fails. Created an issue for this: https://issuetracker.google.com/issues/311925526
14 Views