Closed frederikheld closed 1 week ago
Are you testing the app on a physical device? And are you using a production build? The latter can make a huge difference in performance. I haven't experienced any performance issues (yet) myself.
Note: downgrading to alpha.5 fixed the missing inset bottom and also seems to fix the lag. Messages still there as well.
This is weird, because if you look at the diff, there's not something that points to such a behavior change. The same exact padding values are injected into the client. Also it's hard to imagine that just this line:
val imeHeight = imeInsets.bottom - systemBarsInsets.bottom
would cause a major difference in performance
Please let me know if you are still experiencing issues with this. It would be very helpful
Closing because issue has gone stale
Describe the bug
My app is very unresponsive to user input on Android and I narrowed it down to this plugin. The app also has severe issues when the visible area has to be resized due to opening/closing of the soft keyboard, which seems to be a familiar issue (see #24). It can often take many seconds after the keyboard was closed that the app actually resizes to the newly available space.
Looking at LogCat, I see a constant stream of info messages that appear to be coming from this plugin:
This is only a very small amount of those messages. You can see from the timestamps how frequent they come.
The laggy responsiveness was especially bad with
alpha.3
. Now I have updated toalpha.6
, the responsiveness seems to be improved. But the stream of messages is still there and the safe area inset bottom is does not seem to work anymore. Inset top still works though.Note: downgrading to
alpha.5
fixed the missing inset bottom and also seems to fix the lag. Messages still there as well.Screenshots If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):
Additional context Add any other context about the problem here.