Console: Uncaught (in promise) Error / TypeError / DOMException — unhandled promise rejection
A promise was rejected and no .catch() or try/catch handled it, so the browser logs it as an unhandled rejection.
Uncaught (in promise)Uncaught (in promise) TypeErrorUncaught (in promise) ErrorUnhandled Promise Rejection Meaning
The text after "Uncaught (in promise)" is the real error — often a failed fetch, a TypeError, or code that threw inside an async function. Add error handling at the call site, return the promise so callers can catch, and use the unhandledrejection event to log missed ones.
Common causes
fetchor other async call without.catch/try…catch- Error thrown inside an
asyncfunction that nobody awaits - Rejected promise created by
Promise.rejectand ignored - Extension or third-party script rejecting
- Missing
awaitso the rejection escapes the surrounding try/catch
⚡ Quick fix
- Read the message after "Uncaught (in promise)" to see the real error
- Wrap awaits in
try/catchor add.catch() - Always
awaitorreturnpromises
Detailed fix by platform
JavaScript
try { await load(); } catch (e) { console.error('load failed', e); }- Global net:
window.addEventListener('unhandledrejection', e => console.error('unhandled', e.reason));
Code examples
Handle async errors
async function load() {
const res = await fetch('/api/data');
if (!res.ok) throw new Error('HTTP ' + res.status);
return res.json();
}
// Not handled: load(); -> Uncaught (in promise) Error: HTTP 500
load().catch(err => console.error('load failed', err)); // handledHow to diagnose
- Message — What follows "Uncaught (in promise)"?
- Stack — Which async call created it?
- Await — Any missing await or catch?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- AbortError AbortError: The user aborted a request. / signal is aborted without reason
- Aw, Snap! Chrome: Aw, Snap! Something went wrong while displaying this webpage. Error code: STATUS_ACCESS_VIOLATION / SIGILL / Out of Memory
- captive portal Browser: This network requires you to sign in — captive portal (hotel, airport, café Wi-Fi) blocking HTTPS sites
Most viewed in Browser
Other ways to find it
Where this error sits
Origin: On your device. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 15 Oct 2026