Status Update
Comments
al...@google.com <al...@google.com> #2
Any updates on this? It's been a month already since I reported it, and it seems this crash is occurring quite frequently for my users.
rg...@google.com <rg...@google.com>
ti...@google.com <ti...@google.com> #3
I am still regularly receiving reports about this issue, and it seems it has not been addressed in the latest 1.4.0-rc01 release.
co...@google.com <co...@google.com> #4
Seems like a fairly easy fix on our end. I'll see to that it is fixed in 1.5.
su...@google.com <su...@google.com> #5
co...@google.com <co...@google.com> #6
Sure! Sorry I wasn't clear enough
From
In that case we found that Gboard always included the navigation bar insets (through the systemBars insets) as the IME insets, even in floating mode when the IME navigation bar is hidden, most likely as a workaround for issues like the one mentioned above.
To enable Gboard to remove this workaround on their side, we had to add some logic on the plaftorm side (CL menntioned in
So the fix from Gboard side would be the removal of this workaround which adds the navigationBar insets in Gboard's onComputeInsets
result. I believe this is being rolled out now internally, so I wanted to check when it would be live in prod versions of Gboard
Description
Component used: androidx.core.view.WindowInsetsAnimationCompat Version used: 1.13.0-beta-01 Devices/Android versions reproduced on: Android 14
Attachments:
RootViewDeferringInsetsCallback
the following toast to evidentiate the issue:UnexpectedKeyboardHeightToAnimate.mp4
RightKeyboardHeightToAnimate.mp4
Issue description:
WindowInsetsAnimationCompat#onStart
usingbounds.upperBound.bottom - bounds.lowerBound.bottom
gets us actually the height of the navigation bar when checking for the IME animation bounds.WindowInsetsAnimationCompat#onStart
usingbounds.upperBound.bottom - bounds.lowerBound.bottom
gets us0
(as expected) if checking for the IME animation bounds.Note: I was using the IME animation bounds as a more dependable way to get the keyboard height since as shown in https://issuetracker.google.com/issues/361027506
WindowInsetsAnimationCompat.Callback#onProgress
can sometimes unexpectedly use0
for the keyboard height.