If ToastEmitter is rendered after a call to addToast, all subsequent calls to addToast results in nothing happening. This bug was discovered first in the WorkOrders app after a toast is emitted from failed login-attempts that are done higher up in the render hierarcy
Other info
This bug seems to occur from the locking/unlocking mechanism in the toast queue. If an addToast call is made without an emitter, the onHide callback of the toast is never invoked, meaning that the queue will be locked for ever.
Package / App
Other
Version
mad-toast@latest
What happened?
If
ToastEmitteris rendered after a call toaddToast, all subsequent calls toaddToastresults in nothing happening. This bug was discovered first in the WorkOrders app after a toast is emitted from failed login-attempts that are done higher up in the render hierarcyOther info
This bug seems to occur from the locking/unlocking mechanism in the toast queue. If an
addToastcall is made without an emitter, theonHidecallback of the toast is never invoked, meaning that the queue will be locked for ever.Relevant log output
No response