I'm getting bizarre runtime errors when running on API 22, in an app targeting 21. Extension functio...

# compose

[czuckie]

I'm getting bizarre runtime errors when running on API 22, in an app targeting 21. Extension functions don't seem to be resolvable? (Tried on Java 1.8, 11 and 17, same errors) 🧵

[czuckie]

The code being referenced is coming from an AAR that targets API 34, min 21. Compiled targetting java 17.

java.lang.NoSuchMethodError: No static method weight$default(Landroidx/compose/foundation/layout/RowScope;Landroidx/compose/ui/Modifier;FZILjava/lang/Object;)Landroidx/compose/ui/Modifier; in class Landroidx/compose/foundation/layout/RowScope; or its super classes (declaration of 'androidx.compose.foundation.layout.RowScope' appears in /data/app/com.example.redacted-1/base.apk)

The only other interesting thing which I haven't ruled out yet is, I'm using K2, I'm going to try and not do that and see if the problem persists.

[czuckie]

Even when not using the K2 compiler, I still have this issue ✔️ confirmed

[czuckie]

Row {
  ...
  Spacer(modifier = Modifier.weight(1f))
  ...
}

Is the offending code in the artifact, but if use the exact same expression in the application, it's fine with that. It's only code from the artifact.

Is there special considerations when creating a JC library I'm unaware of?

[czuckie]

doing a binary search for the API level that it finally stops working at. Currently runs as expected on 24 and up.

It doesn't seem to work on 23 and below. (Only tested 23, 22 and 21, 21 being the lowest supported version for JC)

[vide]

what are you referring to with JC?

[vide]

are you running a debug or release build?

[vide]

my team is running compose on api 22 and we haven't seen this issue, we're using kotlin 1.9.10 currently

[czuckie]

debug, just figured it out, it's because of the call to Modifier.weight(1f), without setting the fill parameter to a value, it looks like it's trying to resolve a method with a single parameter

[czuckie]

this is with 1.9.0 and with an imported artifact, rather than a gradle module dependency

[vide]

fill has a default value so it should definitely work

[czuckie]

I'd agree with that statement, I'll try and make a minimal reproduction project

[vide]

Is the artifact built with a matching compose version? we've had some binary incompatibility issues before I think

[czuckie]

yeah using the 2023.08.00 bom

[czuckie]

compose compiler 1.5.0

[vide]

hard to say what the issue is here 🤔

[vide]

we currently use compiler 1.5.3 and target jvm 11

[czuckie]

it could be an emulator issue, on a real device running 5.1.1 it works :X

[czuckie]

I'll still try and put together a small reproduction project

[czuckie]

I managed to make a small repro project for the API21-23 issue with default method arguments being an issue in published libraries that use JC: https://github.com/ChrisAJS/JCApi21IssueRepro

[czuckie]

And a bug report: https://issuetracker.google.com/issues/299833793