Fetch errors are swallowed without logs

[villelahdenvuo]

Before opening, please confirm:

• I have searched for duplicate or closed issues and discussions.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

JavaScript Framework

Not applicable

Amplify APIs

Authentication, GraphQL API

Amplify Categories

auth, api

Environment information

Tested in Chrome with latest Amplify packages.

Describe the bug

Amplify JS SDK swallows fetch errors and simply throws "Network error", even if no network request is ever done. Nothing is logged, unless you turn on DEBUG level logging you see the Auth fetch request fails.

Expected behavior

Actual error message is thrown or the very least an error level log is written.

Reproduction steps

1. Start up an Amplify project (I couldn't find any live demos...)
2. Set log level to DEBUG
3. Override window.fetch and make it throw an error
4. Observe Amplify DEBUG log "Network error" with no details.

Code Snippet

No response

Log output

aws-exports.js

No response

Manual configuration

No response

Additional configuration

No response

Mobile Device

No response

Mobile Operating System

No response

Mobile Browser

.

Mobile Browser Version

No response

Additional information and screenshots

I fixed the error in the fetch request, but finding the error was not easy as I had to spend time debugging a "Network error" even though there was nothing in the DevTools Network tab.

[cwomack]

Hello @villelahdenvuo, and thank you for opening this issue. Based on the comments logged within that screenshot, it looks like we might have this marked on as a known "To Do" to improve the error handling. I'll review this internally and report back soon!

[villelahdenvuo]

@cwomack Hey, I saw the TODO-comment, but I thought I'd raise it also in case it has been missed. Since I did have to spend some hours debugging this, I thought I'd let you know. 😄