Since my script call this UpdateAsync from different points, if the script stops at some line inside it due to an error, with this bug it is impossible to see which part the request came from, thus making debugging difficult.
Intuitive Debugger: Callback Stack stops showing preceding frames when entering UpdateAsync function
2 Likes
Hi, thank you for filing this bug, we added it to our queue.
Does this happen only for UpdateAsync or any other (async) callbacks?
1 Like
I didn’t test, but I think you should.
This is intended functionality. When you are calling a function asynchronously, it is being called on a different thread than the one it was invoked on, and therefore the previous thread cannot be accessed. If we were somehow able to add the rest of the stack, the debugger would not be able to access any variables of that other thread, and we have no guarantees that the thread would even exist by the time the async function is run.
One small way to track where async functions are being called from is by passing in an extra identifier parameter into the function, such a string noting what method/area the method is being called from.