IssueTracker

Jetpack Compose version: BOM 2024.12.01

Jetpack Compose component(s) used: Text in Material3

Android Studio Build: Meerkat Canary 9

Kotlin version: 2.1.0

Problem:

Since bumping target SDK to 35 we notice that some strings on some devices receive unintended line breaks even when the Text Composable is allowed to be as wide as it wants. Trying to force single line does not work either as setting maxLines=1 clip the string rather than join to one line.

Examples of problematic strings:

Actual:ALEX
Rendered:
ALE
X

Actual: Your IKEA
Rendered: 
Your
IKEA

Steps to Reproduce or Code Sample to Reproduce:

Code: Attached minimal reproduction repo including our custom font

Device: Reproduced on Pixel 9 Pro XL real device and emulator using the font/display settings in attached screenshot. Also reported on but not verified: Pixel 8 Pro, Pixel Tablet

Summary of the reprod sample: Activity with the following XML:

<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    android:orientation="vertical"
    android:paddingHorizontal="32dp"
    android:paddingTop="256dp"
    >

    <TextView
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        android:text="TextView: Reproduced by making this string long enough to wrap down to a second line and be above the ComposeView in the parent LinearLayout"
        android:visibility="visible"
        android:layout_marginBottom="16dp"
        android:background="#33FF00FF"
        />

    <androidx.compose.ui.platform.ComposeView
        android:id="@+id/compose"
        android:layout_width="match_parent"
        android:layout_height="wrap_content" />

</LinearLayout>

...and the following sample code:

class ReprodActivity : AppCompatActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        val binding  = ActivityReprodBinding.inflate(layoutInflater)
        setContentView(binding.root)
        binding.compose.setContent {
            Column(
                modifier = Modifier.fillMaxWidth(),
                verticalArrangement = spacedBy(12.dp)
            ) {
                Text(
                    text = "Compose:",
                    fontWeight = FontWeight.Bold,
                    color = Color.Black,
                    fontSize = 14.sp,
                    modifier = Modifier.background(Color.Magenta)
                )
                Sample("Your Test")
                Sample("Your IKEA")
                Sample("ALEX")
            }
        }
    }
}

@Composable
fun Sample(text: String) {
    Row(
        Modifier
            .fillMaxWidth()
            .horizontalScroll(rememberScrollState()),
        content = { repeat(1) { SampleText(text) } },
    )
}

@Composable
private fun SampleText(text: String) {
    Text(
        text = text,
        fontWeight = FontWeight.Bold,
        color = Color.Black,
        fontFamily = MyFontFamily,
        fontSize = 14.sp,
        lineHeight = 22.sp,
        modifier = Modifier.background(Color.Magenta),
    )
}

private val Regular = Font(R.font.noto_ikea_latin_regular, FontWeight.Normal)
private val Bold = Font(R.font.noto_ikea_latin_bold, FontWeight.Bold)
private val MyFontFamily = FontFamily(Regular, Bold)

This will produce the result in attached screenshots.

Some findings from debugging the issue:

• Seems to only be reproducible when combining XML + Compose
• Seems to have occurred after bumping to target SDK 35
• Only some devices are affected and only on some combinations of the display/font size settings
• Only some strings are affected, "Your IKEA" breaks, "Your Test" does not
• Seems to only be reproducible when using our custom font (used without prior issues since 2019)
• In the reproduction sample the issue only occurs if the TextView has more than 1 line of text, if the TextView as 1 line, is Visibility.Gone, removed or moved below the ComposeView in the LinearLayout the issue does not occur.