IssueTracker

private val fontWeights = listOf(100, 200, 300, 400)
private val fonts = listOf(
    "Azeret" to R.font.azeret_mono,
    "Roboto Mono" to R.font.roboto_mono,
)
@OptIn(ExperimentalTextApi::class)
private val fontFamilies = fonts.map { (_, resId) ->
    FontFamily(
        fontWeights.map { weight ->
            Font(
                resId = resId,
                weight = FontWeight(weight),
                variationSettings = FontVariation.Settings(FontVariation.weight(weight))
            )
        }
    )
}

@Composable
fun Demo() {
    Column {
        FullListRepro()
//        FullListOK()
    }
}

@Composable
fun FullListRepro() {
    Column {
        fontWeights.forEach { weight ->
            fonts.forEachIndexed { i, (familyName, _) ->
                val fontFamily = fontFamilies[i]
                val style = TextStyle(
                    fontFamily = fontFamily,
                    fontWeight = FontWeight(weight),
                    fontSize = 40.sp
                )
                BasicText("$weight $familyName", style=style)
            }
        }
    }
}

@Composable
fun FullListOK() {
    Column {
        fonts.forEachIndexed { i, (familyName, _) ->
            fontWeights.forEach { weight ->
                val fontFamily = fontFamilies[i]
                val style = TextStyle(
                    fontFamily = fontFamily,
                    fontWeight = FontWeight(weight),
                    fontSize = 40.sp
                )
                BasicText("$weight $familyName", style=style)
            }
        }
    }
}

OK composable is fine, but if you switch the order you see the incorrect behavior coming from resource font loading.

That issue is a little bit different

We don't do any draw time istantiation of font axes.

You can get the behavior you expect by defining multiple instances of the font. One for each font weight that you want to support. You can put them in a FontFamily, and then matching is done by (FontWeight, Style)

Project: platform/frameworks/support
Branch: androidx-main
Author: Sean McQuillan <seanmcq@google.com>
Link:      https://android-review.googlesource.com/3308947

Don't allow Paint to cache variation settings of resource fonts

Don't allow Paint to cache variation settings of resource fonts 
 
Prev: Loading two resource fonts with the same variation settings would cause the variation settings to not be applied to the second font. 
 
New: Paint cache is invalidated during font load path. 
 
Fixes: b/372044241 
Test: manual of variable font demo 
 
Relnote: "Resource fonts with the same variation settings will now avoid over-caching causing the incorrect variation settings to be applied." 
Change-Id: If3dff4ea44e33b1ed80bc7fb5057923a088f1678

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.compose.ui:ui-text:1.8.0-alpha08
• androidx.compose.ui:ui-text-android:1.8.0-alpha08
• androidx.compose.ui:ui-text-jvmstubs:1.8.0-alpha08
• androidx.compose.ui:ui-text-linuxx64stubs:1.8.0-alpha08