I have a few methods annotated with @OnMain and sometimes it seems like they are having their exceptions eaten. For example; when I was debugging an issue in a game engine project, a loop in a thread would break after 3 iterations, with no exception. On further investigation I was able to fix the issue by making the try-catch look for Exception and it seemed to have fixed the issue.
Clearly Winry was eating the exception and preventing it from bubbling to the surface & presenting itself, and that was very costly to my debugging time.
I have a few methods annotated with
@OnMain
and sometimes it seems like they are having their exceptions eaten. For example; when I was debugging an issue in a game engine project, a loop in a thread would break after 3 iterations, with no exception. On further investigation I was able to fix the issue by making the try-catch look forException
and it seemed to have fixed the issue.Clearly Winry was eating the exception and preventing it from bubbling to the surface & presenting itself, and that was very costly to my debugging time.