Status Update
No update yet.
Comments
jo...@google.com
here is the full error message:
java.lang.NoSuchFieldError: No static field $stable of type I in class Landroidx/compose/foundation/text/KeyboardActions; or its superclasses (declaration of 'androidx.compose.foundation.text.KeyboardActions' appears in /data/app/~~ggrwyg0FaF8w-d1B0cLMgA==/com.example.myapp-SV0HeaEG_BlVBOaRbuFsCw==/base.apk)
at androidx.compose.material3.TextFieldKt$TextField$2.invoke(TextField.kt:206)
at androidx.compose.material3.TextFieldKt$TextField$2.invoke(TextField.kt:186)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke(ComposableLambda.jvm.kt:107)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke(ComposableLambda.jvm.kt:34)
at androidx.compose.runtime.CompositionLocalKt.CompositionLocalProvider(CompositionLocal.kt:228)
at androidx.compose.material3.TextFieldKt.TextField(TextField.kt:186)
java.lang.NoSuchFieldError: No static field $stable of type I in class Landroidx/compose/foundation/text/KeyboardActions; or its superclasses (declaration of 'androidx.compose.foundation.text.KeyboardActions' appears in /data/app/~~ggrwyg0FaF8w-d1B0cLMgA==/com.example.myapp-SV0HeaEG_BlVBOaRbuFsCw==/base.apk)
at androidx.compose.material3.TextFieldKt$TextField$2.invoke(TextField.kt:206)
at androidx.compose.material3.TextFieldKt$TextField$2.invoke(TextField.kt:186)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke(ComposableLambda.jvm.kt:107)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke(ComposableLambda.jvm.kt:34)
at androidx.compose.runtime.CompositionLocalKt.CompositionLocalProvider(CompositionLocal.kt:228)
at androidx.compose.material3.TextFieldKt.TextField(TextField.kt:186)
Description
Jetpack Compose version: 1.3.1
Jetpack Compose component used: androidx.compose.material.pullrefresh.PullRefreshIndicator
Android Studio Build: Android Studio Electric Eel | 2022.1.1 Beta 5. Build #AI-221.6008.13.2211.9237616, built on October 31, 2022
Kotlin version: 1.7.20
This issue is not 100% reproducible but it happens quite often when the indicator is shown and the loading time is short (e.g. The content is already cached).
This issue is pretty annoying because the
SwipeRefreshform Accompanist got deprecated but this new official way is now bugged. The Accompanist implementation is not affected by the issue, but it now triggers deprecation warnings every time it's used.Steps to Reproduce or Code Sample to Reproduce:
PullRefreshIndicatoras it is shown on the Google Official guidelines (delay(1500)) until 5-10msPullRefreshIndicatorremains on screen until user touches screenYou can find a sample project here:https://github.com/jarroyoesp/SwipeRefresh
Attached you can find videos showing the issue (on both the sample project and our production application).