-
Notifications
You must be signed in to change notification settings - Fork 163
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
TypeError: Failed to fetch Object.startKeepAliveServiceWorker #1392
Comments
Hi @HSULGIT thank you for your issue. Do you have a sample of your configuration and also you trusted domain.js? |
the "Failed to normalize url" is gone, but the failed fetches on
remaining. This happens while development and with the deployed build on the server. Here is my trusted domain file and the configuration. OidcTrustedDomains.js (urls replaced with placeholders here (except 127.0.0.1))
And my configuration (Authentication.tsx):
AppBar.tsx:
Hope that helps to track down the issue on Object.startKeepAliveServiceWorker. Thank you helping! |
Till now i sadly get this error. All others are solved. TypeError: Failed to fetch It seems to happen when using @guillaume-chervet: Is there a solution to the Problem or are you still investigating on it? Btw thanks for your great work with the package. The minSleepSeconds problem disappeared after updating to the newest version. |
I now switched from CRA to VITE, but the Problem seems to remain the same again:
Are there any new updates on this @guillaume-chervet? It happens on logout: const { idTokenPayload, idToken } = useOidcIdToken();
|
Issue and Steps to Reproduce
OidcServiceWorker.js:19 Failed to normalize url: undefinednormalizeUrl @ OidcServiceWorker.js:19
getCurrentDatabasesTokenEndpoint @ OidcServiceWorker.js:291
handleFetch @ OidcServiceWorker.js:367
When user gets redirected to keycloak login and put in credentials and hit login, the redirect to the next page (react-oidc secured component) causes the error seen above. Seems that i tries to inintialize the auth but the OidcTrustedDomains config is not loaded in time for the OidcServiceWorker. Only happens after login on auth provider. When reloading website no error occurs.Also i got a non Error in console on that:
After that also the fetching of "/.well-known/openid-configuration" from auth provider which is present and available, fails.
When following the url there is the openid-configuration present.
Also the fetch on "https://myDomain.de/OidcKeepAliveServiceWorker.json?minSleepSeconds=150" fails, like mentioned here (no OidcKeepAliveServiceWorker.json is present in public folder): #1355
What could lead to this problems?
Versions
7.13.6
Additional Details
The text was updated successfully, but these errors were encountered: