Description
If the process receipt callback yields (e.g. task.wait()) and throws an error afterwards, that error message doesn’t show on the output console.
Repro
ReproPlace.rbxl (32.6 KB)
I’m sharing a file that reproduces the problem 100% of the times on my PC (Windows 10). The place triggers a purchase when you join as a player (open on studio to avoid wasting Robux). After you purchase the product on Studio, the first print message from the process receipt callback is printed on the console, but the error message isn’t printed. The second print also doesn’t appear because the callback halted on the error. So, thinking in real case scenario, if the callback throws an error, you have no idea the process receipt callback is the source of the error and even if you are able to establish that because the player didn’t receive the product, you don’t know where the error happened.
This is not a Message/Context console filtering problem. The same place has a disabled “Normal Script”. If you enable it, you will see its error message after the script yields.
If there is anything more I can do to help, feel free to contact me.