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.

Please check my example. I reproduced the crash in my pixel 6a 14. Click the edit text and then click the keyboard done.

George, would you mind checking the example in #comment10 to confirm whether your fix addresses the issue?

I am able to repro with the given project.

The problem is that ComposeView assumes that its contents are focusable. As a work-around, I think that if you call view.focusable = false after instantiation, you won't have this problem.

What version will this be addressed in?

+1. The workaround isn't practical for us as we have many unique ComposeViews. This issue is blocking Compose library upgrades for us.

#comment14 that fix isn't doing the trick :(

someone had success with getting at the AndroidComposeView inside the ComposeView here.

something like this maybe - is this a legit workaround?

composeView.doOnAttach {
   (it as ViewGroup).getChildAt(0).isFocusable = false
}

Ok, so I see this note in androidx.compose.ui:ui:1.8.0-alpha03 release notes:

Fixed exception thrown when the IME is active on an external View and the Next action is used to enter focus on the ComposeView. The clearFocus() behavior aligns with View behavior on API < 28, where clearFocus() can cause the default View to be focused.

So it might be fixed? Has anyone tried?

The CL is still in review.

Thanks #comment19! Is it possible to include this fix in a stable version of the library? Wondering if there's an ETA on this... We are currently seeing the issue spike a lot in the wild - very hard to repro locally so if we could put it in a stable BOM version that would be ideal - we are weary of using alpha versions for fears of other instabilities.

The fix that seems to be working for us is adding Modifier.focusable() to the root composable in our custom AbstractComposeView for cases where focus is needed but the crash is still happening. Verified with #comment10's minimal repro that this works. But this is very impractical as we too have so many ComposeViews in our app.

Any updates on cherry picking this fix in a stable version? We are still seeing a lot of crashes for users in production.

Project: platform/frameworks/support
Branch: androidx-main
Author: George Mount <mount@google.com>
Link:      https://android-review.googlesource.com/3329475

Stop crash when moving focus to ComposeView with no focusable content

Stop crash when moving focus to ComposeView with no focusable content 
 
Fixes: 369256395 
Fixes: 378570682 
 
Compose advertises itself as focusable. When another View finds the 
ComposeView and requests focus on it, it is expected to accept the 
focus and can crash if it doesn't. This CL returns true when that 
happens and tries to move focus to the next item if possible. 
 
When moving focus between ComposeViews using "Tab," the 
focus was not changing. This CL fixes that problem. 
 
Test: new test, manual testing 
Change-Id: I372b6974e1b4714f825c208e683aea8d50e19116

I found the above changes were reverted. https://android-review.googlesource.com/c/platform/frameworks/support/+/3376809

Which release is this fix available in?

I opened a similar issue if not the same back in August. It was opened before the bug was introduced into the stable release of compose UI 1.7.0 at the end of August: https://issuetracker.google.com/issues/363189655

That was marked fixed for some reason and the developer suggested me to open a new issue as he was convinced that he fixed it. So I opened a new one with more details at https://issuetracker.google.com/issues/378542627

Now someone pointed out that there is this issue too.

Project: platform/frameworks/support
Branch: androidx-main
Author: George Mount <mount@google.com>
Link:      https://android-review.googlesource.com/3386976

Fix several focus issues

Fix several focus issues 
 
Fixes: 369256395 
Fixes: 378570682 
Fixes: 376142752 
 
Relnote: "Fixed several focus-related issues, including 
crashes when IME tries to focus on ComposeView without 
focusable items, focus change within child AndroidViews, 
and focus request leaving an AndroidView." 
 
Allow focus to leave AndroidView using requestFocus() 
When requestFocus() is called to move focus from an 
Android View within Compose to a compose focus requester, 
the ComposeView should be focused and the focus target 
should have focus. 
 
This CL moves the functionality for moving focus 
between child Views to the key handler, moveFocus(), 
and requestFocus(). 
 
Test: new test, manual test 
Change-Id: Ia03c3c04dc9fd9d55d8fcae6b15e15cb2384f467

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

• androidx.compose.ui:ui:1.8.0-alpha07
• androidx.compose.ui:ui-android:1.8.0-alpha07
• androidx.compose.ui:ui-jvmstubs:1.8.0-alpha07
• androidx.compose.ui:ui-linuxx64stubs:1.8.0-alpha07

Are there any plans to backport it to 1.7?

George: what do you think about backporting this fix to 1.7? Does aosp/3329475 introduce a lot of risk?

I think it is fine, but it has been reverted, so we should wait until it lands with stability.

🙏🏼 Backporting this fix to a stable release would be greatly appreciated! Adopting an alpha version isn't available to us due to stability concerns.

Any updates on this issue?

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

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

Any plans to backport this to 1.7?

removed

Nevermind, i read this wrong.