IssueTracker

First of all thanks for this detailed issue.

This issue had been investigated thoroughly when it was first reported internally. The surprising detail in this report is that the issue is not reproducible before 1.7. I will look into this.

The main problem with POBox is the fact that it is deprecated. Since 2021 Sony has been shipping new Xperia devices with Gboard pre-installed. Although we are aware that there is still a considerable amount of users still using POBox, the described behavior is caused by POBox's noncompliant behavior with InputConnection and InputMethodManager documentation. However, this is understandable since TextView implementation was also not respecting the behavior that is expected from Editors.

Ultimately we have decided to enforce the documented behavior with specifically regards to when editors should call InputMethodManager.updateSelection. Also, although unconfirmed, there were traces of possible custom code being included in Sony OEM images that changed how InputMethodManager was notified from TextView. If POBox also depended on something like this, it would be impossible for Compose code to replicate the same unknown behavior.

Just to be sure, it is dangerous to replace Compose TextField with Android View EditText as a workaround for this issue.

Compose 1.7 has a bug that causes ANR when the focus is on EditText. https://issuetracker.google.com/issues/369354336

Another View-related bug in Compose 1.7 is that an Android View is focused by calling FocusManager.clearFocus(). https://issuetracker.google.com/issues/374031296

Perhaps there is a lack of testing of Compose 1.7 in combination with Android View. There is also a possibility that there are other fatal bugs related to View.

In other words, the only options for apps targeting the Japanese market that require POBox support are to continue using Compose 1.6 or to use EditText in combination with various workarounds.

Project: platform/frameworks/support
Branch: androidx-main
Author: Halil Ozercan <halilibo@google.com>
Link:      https://android-review.googlesource.com/3317256

Fix POBox keyboard issue

Fix POBox keyboard issue 
 
Fix: 373743376 
Fix: 329209241 
Test: NullableInputConnectionWrapperTest 
Change-Id: I94e0e598274fb88b255f977f9fbd50dfbbb1ecb1

Many thanks again for this report. Especially for giving us a huge clue in terms of what could be going wrong. The fix is now merged and I will ask for a cherry-pick into a stable release.

Yes, this fix is planned to be included in a future 1.7.x release.

Thanks for the fix. Sorry to follow up on this. is it possible for you to share specific release version/date for the stable version? We are waiting on this to decide on our direction.

Same result for google-sans-text-medium

Text(
            text = "GGGGG google-sans-text-medium",
            fontSize = 60.sp,
            fontFamily = FontFamily(
                Font(
                    DeviceFontFamilyName("google-sans-text-medium"),
                )
            )
        )

I've confirmed on Pixel 6 that "google-sans-text-medium" loads a GS text font - see attached.

Can you get a minimal repro for this one? It looks likely that it could just be using the wrong font at that application.

Reproduced by loading in background. Appears related to DeviceFontFamilyName variation setting from a background thread leaking somehow.

For Google Sans Text please specialize the opsz when loading it.

You can either

1. Disable load-time font variation settings

@OptIn(ExperimentalTextApi::class)
val GoogleSansText500Medium = Font(
    DeviceFontFamilyName("google-sans-text-medium"),
    weight = FontWeight.W500,
    variationSettings = FontVariation.Settings() /* don't specialize font variation, leaving opsz alone */
)

2. Intentionally specialize the font variation settings, including explicit opsz

@OptIn(ExperimentalTextApi::class)
val GoogleSansText500Medium = Font(
    DeviceFontFamilyName("google-sans-text-medium"),
    weight = FontWeight.W500,
    variationSettings = FontVariation.Settings(
        FontWeight.W500,
        FontStyle.Companion.Normal,
        // opsz <=17f for Google Sans Text
        // opsz >=18f for Google Sans
        FontVariation.Setting("opsz", 17f)  
    )
)

What's going on

When opsz is not provided, the default behavior of specializing variation settings to (Weight Style) causes opsz to be reset to the default value, which is "Google Sans"

By explicitly skipping variation settings, or setting opsz you're ensuring that either (1) the system loaded typeface or (2) the desired specialization is used exactly.

This bug was linked in a change in the following release(s):

• androidx.compose.ui:ui-text:1.3.0-rc01