Fixed
Status Update
No update yet.
Comments
ry...@google.com
ap...@google.com
There's some code in the tracers:
com.swissborg.app.common.compose.navigation.NavigationAnimationsKt$offsetXFactor$1 in invoke-3p2s80s at line 24
com.swissborg.app.common.compose.navigation.NavigationAnimationsKt$offsetXFactor$1 in invoke at line 23
Woudl you be able to link it or provide a similar code to what you have to help us debug further? How offsetXFactor looks like as well as your custom navigation logic and how it swaps the screens
Description
The blocking bug relates to incorrect bytecode generated for hashCode() calls on certain API levels. Because of this, there is an otherwise unnecessary manual hashCode implementation. Once the blocking bug is resolved, we should remove it.