https://kotlinlang.org
Join Slack
Anyone else seeing random crashes when using any M3 `TextField` (Compose `1.4.0-alpha04`)?
# compose
z
Anyone else seeing random crashes when using any M3 
TextField
(Compose 
1.4.0-alpha04
)?
Copy code
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/~~Ryd15-x8fYvP8Rc3u4Of2g==/x.x.x-AjN2HUwfoOTGS8EQxcnlNg==/base.apk)
z
Known issue, will be fixed in next release. Are you using the latest version of the material artifact?
z
Got it! Known as in its been there for a while? Havent noticed it until upgrading. Same version for M3.
z
Upgrading m3 to latest version should workaround it
e
Isn't 1.4.0-alpha04 the latest version?
Oh it's 1.1.0-alpha04
z
Thank you.. I forgot that they were using different versions!
z
Yep. Both libraries are affected, upgrading to the newest versions fixes both. The newest versions are: Material: 1.4.0-alpha04 Material3: 1.1.0-alpha04
This is a weird bug because it’s a compiler bug that breaks backwards compatibility of the foundation artifact. It was already fixed before these were even released, but the release had already been cut, so the fixed artifact will only be the next release. Any libraries that depend on foundation and use 
KeyboardActions
will also probably be affected, until the next compose release.
We’ll be updating the release notes to mention this issue soon.
e
So Material 1.4.0-alpha04 and M3 1.1.0-alpha04 shouldn't be used if you use a TextField?
z
No, those are the latest versions, they are the only ones that should be used with the 1.4.0-alpha04 releases of other compose artifacts.
e
Oh I see, thanks!
23 Views
Open in Slack
PreviousNext
Powered by

kotlinlang

A modern programming language that makes developers happier.

Powered by