Fixed
Status Update
Comments
st...@google.com <st...@google.com> #2
I hit this exact stacktrace too. I have a pretty simple app with the only complex screen being a lazygrid layout. not sure what the root cause here could be.
st...@google.com <st...@google.com> #3
As you can see it's been a long time and they do not even answer.
The workaround that is still needed is simple. Since this is a relatively rare issue and not a single user ever contacted about that issue before or after the workaround I guess it's good enough for now.
@SuppressLint("RestrictedApi")
override fun dispatchKeyEvent(event: KeyEvent): Boolean {
return runCatching { super.dispatchKeyEvent(event) }.getOrDefault(false)
}
ap...@google.com <ap...@google.com> #4
We recently landed significant changes to the affected code paths. The changes have not been released yet. Can we ask you to either wait for the next alpha release or try one of the latest snapshots?
Thanks!
Description
Version used: 1.0.0-alpha12
Devices/Android versions reproduced on: Galaxy Watch 4 Classic
By default,
rememberSwipeDismissableNavController()
does not seem to support back button on watches that have it (for example Galaxy Watch 4). When user presses back button, whole activity will exit.Workaround is to manually add BackHandler after creating the nav controller: