Closed fran893 closed 7 months ago
This is a unique issue to this sample, not with the base implementation of the AdapterWithErrorHandler. In this sample if the AdapterWithErrorHandler tries to send an Activity through the middleware it gets caught in the translation step again, which is the cause of the initial error, so nothing is output. To fix this this sample needs to send any error message Activities without using the middleware. Best course of action is to create a new AdapterWithErrorHandler just for this sample, and implement the setOnTurnError in a way that doesn't send through the middleware. This will not require changing the base AdapterWithErrorHandler that is part of the SDK.
Awesome @LeeParrishMSFT! Thanks for the information, we will review it as soon as we tackle the issue just for this sample 😊.
@LeeParrishMSFT we don't have permissions to transfer this issue back to botbuilder-samples but feel free to do it.
We will be updating the description of this issue in order to detail the samples that need to be updated 😊!
Java retired Nove 2023. The Java Samples are no longer maintained.
Sample information
Describe the bug
When a sample has an error, some of them are not captured by the AdapterWithErrorHandler, generating an
HTTP 500 error
and the error's activities are not displayed in the Emulator.To Reproduce
Steps to reproduce the behavior:
Expected behavior
The expected behavior is that when an error occurs, the AdapterWithErrorHandler should capture it and the error activities should be displayed in the Emulator, like C#.
Screenshots
AdapterWithErrorHandler issue in Java samples
Expected behavior in Java (like C#)