GWT 2.8.2 - JsInterop and Stacktraces

69 views
Skip to first unread message

Thomas

unread,
Aug 11, 2020, 2:51:21 AM8/11/20
to GWT Users
Hi,
I'm slowly moving to using more and more JsInterop instead of JSNI in our application (I know, I'm late).
The app has a so far reliable uncaught exception handler (GWT.setUncaughtExceptionHandler) and we use $entry for callbacks from JSNI.

But when getting an exception in a JsInterop callback, the exception and stack trace are now totally unusable (in SuperDevMode):
Throwable.java:120 Uncaught Error: java.lang.RuntimeException
    at RuntimeException_1_g$.createError_0_g$ [as createError_2_g$] (Throwable.java:120)
    at RuntimeException_1_g$.initializeBackingError_0_g$ [as initializeBackingError_1_g$] (Throwable.java:112)
    at RuntimeException_1_g$.Throwable_1_g$ (Throwable.java:60)
    at RuntimeException_1_g$.Exception_1_g$ (Exception.java:25)
    at new RuntimeException_1_g$ (RuntimeException.java:25)
    at Function.onSuccess_383_g$ (BrowserFileSystemPlatform.java:78)
    at lambda_0_g$ (Runtime.java:166)

Obviously there is no $entry around the callbacks.How can I fix this and get usable stack traces again?

Thanks,
Thomas
Reply all
Reply to author
Forward
0 new messages