You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is because of the simple way 'AfterHotReloadEffect' handles itself being removed.
Right now, removing the 'AfterHotReloadEffect' from a composable
will still have the listener instance registered, trying to call the stastic lambda method potentially resulting in Exception in thread "AWT-EventQueue-0" java.lang.NoSuchMethodError: 'kotlin.Unit SomeWidgetKt.SomeWidget$lambda$1$lambda$0().
Therefore, the 'AfterHotReloadEffect' will ignore such linkage errors, assuming that it is invalid now.
A better solution has to be found which will not swallow user space linkage errors.
The text was updated successfully, but these errors were encountered:
This is because of the simple way 'AfterHotReloadEffect' handles itself being removed.
Right now, removing the 'AfterHotReloadEffect' from a composable
e.g. from
to
will still have the listener instance registered, trying to call the stastic lambda method potentially resulting in
Exception in thread "AWT-EventQueue-0" java.lang.NoSuchMethodError: 'kotlin.Unit SomeWidgetKt.SomeWidget$lambda$1$lambda$0()
.Therefore, the 'AfterHotReloadEffect' will ignore such linkage errors, assuming that it is invalid now.
A better solution has to be found which will not swallow user space linkage errors.
The text was updated successfully, but these errors were encountered: