You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TypeError: Failed to fetch
at window._sentryFetchProxy (<anonymous>:4:56)
at window.fetch (<anonymous>:5:51)
at window.fetch (/_app/immutable/entry/start.ea20df43.js:1:1551)
at C (/_app/immutable/chunks/gfetch.63a7660f.js:2:4469)
at None (/_app/immutable/chunks/gfetch.63a7660f.js:2:4972)
...
(12 additional frame(s) were not displayed)
The failed to fetch error in this sentry report appears to have happened in /api/auth/proxy.
this route uses isomorphic-fetch directly without retries. We should add a fetch-retry library to this fetch.
update:
Reading through the Sentry report again, it loos as though the call to https://thatconference.com/api/auth/proxy is what is generating the failed to fetch error. It doesn't appear that https://thatconference.com/api/auth/proxy was called in this case. It failed to be called.
The text was updated successfully, but these errors were encountered:
Sentry Issue: THATCONFERENCE-COM-JS
The
failed to fetch
error in this sentry report appears to have happened in /api/auth/proxy.this route uses isomorphic-fetch directly without retries. We should add a fetch-retry library to this fetch.
Either directly add fetch-retry or use gfetch?
code: https://github.com/ThatConference/thatconference.com/blob/main/src/routes/api/auth/proxy/%2Bserver.js
update:
Reading through the Sentry report again, it loos as though the call to
https://thatconference.com/api/auth/proxy
is what is generating the failed to fetch error. It doesn't appear thathttps://thatconference.com/api/auth/proxy
was called in this case. It failed to be called.The text was updated successfully, but these errors were encountered: