When using

TextField

, I randomly get cases where the keyboard doesn’t come up, is it a know issue ? do I need to do something special ?

It is a known issue

oh ok thanks, is there a workaround for this ?

It's really bad in terms of UX, when will it be fixed? Do we have Issuetracker link which I could star?

I do not know unfortunately

yeah I mean that’s what happens when you live on the edge of the alpha 😅 but thanks everyone, glad to know it’s coming up

Yes of course, it's still an alpha 🙂

Actually it seems that https://android-review.googlesource.com/c/platform/frameworks/support/+/1456460/ was shipped in Alpha 09, right? So it still does not fix the issue.

I think this is another issue. It is more related to switch focus between two TextField. But my issue with keyboard opening for the first time.

Yep, but that issue persists even after mentioned patch

Can you please create a ticket?

@Siyamed does the team not know about this bug? we’ve had reports of the problem on every device from Samsung A20 on Android 10 to my Pixel 4a on Android 11

I dont follow, is there a ticket that i am not aware of?

this issue has been around for months, it happens literally 50% of the time i am building the app, it would shock me if the dev team does not know about such a huge problem. users literally have to restart their devices to get the keyboard to show up

Anyways, have a nice day.

what could be a bigger problem than getting the keyboard to show up?

Sam you're being super rude. Just file a bug.

"one issue the prevents apps from shipping -- keyboards that don’t open is an egregious violation of user experience and expectations" Sam its called an Alpha

"the compose devs + evangelists (cc @Leland Richardson [G]) should know this is the number one issue the prevents apps from shipping -- keyboards that don't open is an egregious violation of user experience and expectations" 😂 I can't even enable compose in my project due to a bug in AGP. I DEMAND that it be fixed immediately!

Happens to me quite a bit as well. I’m sure the team is tracking it somewhere.

Hence why @Siyamed asked if you could make a bug report

@Robert Menke i think that’s precisely the disconnect here, it’s not being tracked. for the record i didn’t write a bug report because everyone said this issue was tracking it

found this one which sounds similar to the problem: https://issuetracker.google.com/issues/170188271

this is exactly the issue @Siyamed thx for finding the report

A factor in this is that several of the lower-level subsystems that need to work together for soft keyboard operation in text fields have been undergoing major rework/refactoring over the past several months. What looks like a lack of movement on this is due to the work happening at those lower levels, so that we can fix it (hopefully) once, rather than patch what is there currently, possibly creating new dependencies on older implementation details we are trying to turn down in the process.

@Adam Powell that’s really helpful information, thanks for sharing. in the meantime it would be great to know what your best hack is to mitigate the problem until the refactoring is finalized. @Cyril Find came up with adding clickable to the parent

Row

and calling

requestor.requestFocus()

but is there a better way?

not sure off the top of my head, I'm afraid. Us googlers are on a company holiday today so our answers are likely to be a bit hand-wavey until we all get back to work officially later this week

Hi @Adam Powell and @Siyamed, circling back around here — is there a recommended workaround? If not, where will a workaround be posted when one becomes available?

People: Is compose ready for production? Compose team: No. People: hold my beer

@Colton Idle do you have anything worthwhile to contribute or is every comment going to be passive aggressive and deterring

folks, the sniping isn't necessary. We'll let you all know when there's more to share; ideally with a, "fixed" note in some release notes. 🙂

appreciate the clarity @Adam Powell. we will continue to use the partial workaround from @Cyril Find until it’s fixed

A fix landed for https://issuetracker.google.com/issues/170188271 . It will be present in alpha11 (and it's already present in today's http://androidx.dev snapshot builds if you need it faster). Please let us know if you notice a remaining keyboard open/dismiss bug that we failed to cover with this fix

Cool ! Ok i’m going closer to the edge, let’s try snapshots, hold my coffee 😁

@Cyril Find here is the guide for using accompanist with snapshots: https://chrisbanes.github.io/accompanist/using-snapshot-version/

hey @Alexandre Elias [G] thanks I saw that but I still didn’t make it work 😅 but it’s fine I just tested the fix, I can wait for alpha11 for now 🙂

@Alexandre Elias [G] i tried that guide as well, but was also unsuccessful at compiling