New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to get http error response code: 4XX #3693
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
bump |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
bump |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because of inactivity. Please open a new issue if are still encountering problems. |
Did you resolve your issue ? Unless you have cors problem, I think you have to catch your error in your lambda and send it with headers. You did use amplify API correctly. |
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
Describe the bug
When Api fails with network error, for example 413, the error object doesn't contain error response code. Error is caught but not enough information such as error response code is provided by error object.
To Reproduce
When I uploaded with payload over lambda size limit, I expected to get 413 error code but I couldn't retrieve 413 from the error code.
Expected behavior
Expected to be able to retrieve error response code
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
It could be just an issue with Axios
axios/axios#1427
Sample code
Include additional sample code or a sample repository to help us reproduce the issue. (Be sure to remove any sensitive data)
You can turn on the debug mode to provide more info for us by setting window.LOG_LEVEL = 'DEBUG'; in your app.
Let me know if I use Amplify API incorrectly or you need more information. Thank you.
The text was updated successfully, but these errors were encountered: