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.

I just checked again on beta09 and it's still here. I couldn't reproduce it on an emulator but it happens on my real device only the first time the keyboard opens (app must be force closed).

Also when the keyboard does not fully cover the TextField, it still has inconsistent placement as I just reported on issue #191286850 before knowing the main bug is still here. (The attached files show the issue)

soboleva@

Did you try this on the latest build? Haoyu merged the change in Jun 15, we reopened in Jun17 based on beta09. Is the change in beta09?

Hi, thanks for the updates!
IIRC the change is after beta-09 cut and will come with beta-10.
Meanwhile, the consistency issue mentioned may not be fixed by the CL above.
The possible course of the b/191286850 might be the timing we call the notifyFocusedRect. So far I haven't confirm the course of the issue yet.(Might be the timing we call requestRect or it's because requestRect is called multiple times) Will update the progress on b/191286850.

Not sure what is consistency issue. But I tested today on tip of androidx-main branch and the issue described in the ticket is still reproduced 100% times.

Tested on device with API 30.

I just updated my app to 1.0.0-rc1 and the issue is still happening. The input field isn't visible sometimes.

I can reproduce using the demo app on the latest main branch, but as mentioned above it only happens the first time a text field is focused after launching the app, subsequent focuses move the text field into view as expected, and only on some API versions (24, not 30).

If you're still seeing this bug, is your window's soft input mode ADJUST_RESIZE or ADJUST_PAN?

I have activity soft input mode set to adjustResize as per accompanist insets lib: https://google.github.io/accompanist/insets/

This is close enough to b/192043120 that I'm going to mark it as a duplicate.