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
It seems, that in version 6 it is not possible to propagate event in event-listeners, when one of them throws an exception. Resetting EVENT_PARAM_EXCEPTION allows us to handle thrown exception (log it or whatever) thus stop it from bubbling back to the app, but it won't help to continue with invoking the rest of registered listeners.
The text was updated successfully, but these errors were encountered:
If @prolic is not faster I can check the issue in 3-4 hours. Should be possible to catch exceptions and continue with the rest of the listeners, but maybe we've introduced a bug by cleaning up the message dispatch process. Thx for the bug report
It seems, that in version 6 it is not possible to propagate event in event-listeners, when one of them throws an exception. Resetting EVENT_PARAM_EXCEPTION allows us to handle thrown exception (log it or whatever) thus stop it from bubbling back to the app, but it won't help to continue with invoking the rest of registered listeners.
The text was updated successfully, but these errors were encountered: