Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Wrong exception type thrown in GWT backend ReflectionCache.forName
See original GitHub issueDocumentation for reflect.ClassReflection.forName states that it throws ReflectionException and does so in native java implementation
https://github.com/libgdx/libgdx/blob/0acff984c84cf7a8765603865dadbe7ba987c8cd/gdx/src/com/badlogic/gdx/utils/reflect/ClassReflection.java#L29-L31
However, the GWT implementation throws a RuntimeException
https://github.com/libgdx/libgdx/blob/0acff984c84cf7a8765603865dadbe7ba987c8cd/backends/gdx-backends-gwt/src/com/badlogic/gwtref/client/ReflectionCache.java#L49-L51
This is an inconsistency and GWTs implementation should follow the doc.
This can probably be fixed by gwt reflection cache throwing a ClassNotFoundException, which would get caught by
https://github.com/libgdx/libgdx/blob/0acff984c84cf7a8765603865dadbe7ba987c8cd/backends/gdx-backends-gwt/src/com/badlogic/gdx/backends/gwt/emu/com/badlogic/gdx/utils/reflect/ClassReflection.java#L30-L34
Please select the affected platforms
- Android
- iOS
- HTML/GWT
- Windows
- Linux
- macOS
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I can, PR incoming sometime then.
This should be an easy change, do you want to file a PR @nojus297