Access the stack trace of an error from outside of a UniTask?

[spherous]

I'm new to a project that's using this system, so I didn't write the code causing the error, and do not know what code is even causing the error.

I have a nullref being thrown, and I'd love to see what field is null in what script so I can begin to actually fix it, but the entire error is captured in the UniTask completely obfuscating what caused it, and the stack trace starts at the UniTask.Run() call. I want the stack trace that has the nullref in it from outside of the UniTask, how can I get such a thing? Could I change UniTask erroring to always output the calling stack instead of it's internal stack (which means absolutely nothing to what's actually causing the error, making debugging far harder than it needs to be), if so, how?

Here's an image of the stack trace it's giving me