-
Notifications
You must be signed in to change notification settings - Fork 21
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
[Bug - next-pwa]: FetchEvent.respondWith received an error #79
Comments
|
I see! Thanks for the quick reply. There is this Stackoverflow post:
This seems to align with what we are seeing as well, as only Safari users have reported issue and the sporadic nature can be explained by a spotty connection. This might just be a Safari bug but I wonder if there is some way to more gracefully avoid this failure. |
@aaronabf went through the repo and yeah, maybe it's due to a slow internet connection. I honestly don't know why this is happening and how to fix it either. Seems like a Workbox or Safari issue because I've not found anything in the repo that could be causing this :( Maybe some help on reproducing would do the trick. |
@DuCanhGH It seems to go away whenever you clear the browser cache. Once someone hits it, they will consistently have the issue until the cache is cleared. |
@DuCanhGH any updates as to why this might be happening? it's not a good UX to tell users to clear their cache when this happens. Ideally it goes away without having to clear the cache. |
@pz129 I haven't a clue either. This can't really be reliably reproduced, so there's that. |
@aaronabf can I have your addFetchListener() {
self.addEventListener("fetch", (t) => {
const { request: e } = t,
s = this.handleRequest({ request: e, event: t });
s && t.respondWith(s);
});
} They made sure that the response is defined before calling |
Huh that's really odd. Our configuration is fairly minimal:
And the |
This issue is stale because it has been open for 30 days with no activity. |
|
Provide environment information
Link to reproduction - Issues with a link to complete (but minimal) reproduction code help us address them faster
n/a
To reproduce
We are unable to successful reproduce the issue.
Describe the bug
We run this fork of next-pwa and are having users sporadically seeing this error message in Safari:
My best guess is it's an issue with this code block here, but I do not know this codebase very well.
Expected behavior
For this error to not surface.
Screenshots (if relevant)
No response
Additional information (if relevant)
No response
The text was updated successfully, but these errors were encountered: