I wasn’t really sure how to categorize this, so apologies if this is the wrong category.
Recently (after working through an issue from a different thread), I came across a problem attempting to load a font asset. I made sure I was loading the correct file, but there was some error when loading the associated image data. At the time, all it said was something to the effect of ‘AssetLoadException: An error occurred while attempting to load the asset’ (this may be minorly paraphrased, as I hadn’t thought to take screenshots at the time).
I puzzled over how to interpret this vague error, which led me to dive into the Javadoc. It turns out that AssetLoadExceptions have a reference to a ‘cause’ - a separate exception that was, well, the cause of the error. In order to read this ‘cause’, though, I had to wrap my existing code in a try:catch block, catch the AssetLoadException, and print the stack trace of the cause. This gave much more useful information that enabled me to fix the problem immediately. (The actual error that occurred was that my image data was formatted incorrectly [it used indexed color instead of full color, which wasn’t supported], but that’s beside the point.)
If I could make a suggestion/feature request, I’d request that AssetLoadExceptions (and other exceptions that have ‘Cause’ fields) display the message from their cause (if one exists) in addition to the existing stack trace. This would have made the debugging process easier in this case, and likely in others as well.