-
Notifications
You must be signed in to change notification settings - Fork 27
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
newbie - errors #5
Comments
@acerov what browser were you using? did you put your rest server api in the dynamicCache section in your environment.js file? |
@jkleinsc chrome 46.0.2490.86 m, but I tried with firefox also (service worker not supported), in environment.js I have: |
You could try adding the debug option in environment.js to add console logging to see where the caching is failing:
|
@jkleinsc thank you for your effort but with |
Are you seeing any output in the developer console? debug:true adds console statements to the service worker so you can see what it is attempting to do. If you are not seeing any additional output try doing a refresh/hard refresh in your browser. |
I had to go to chrome://inspect/#service-workers and click inspect and there are the same errors: |
@acerov I am refactoring the code to use https://github.com/GoogleChrome/sw-toolbox which should resolve this issue. I will let you know when that update is available. |
@jkleinsc great, I will be happy to test it :) |
@acerov I just published a new version 0.0.5 which should resolve your issue. Let me know if you still run into problems. One thing of note, the configuration has changed slightly - includePaths is now called precacheURLs. |
@jkleinsc what can I say, it just works :) thank you! |
Hi,
I am totally new to serviceworker. Just installed broccoli-serviceworker following the instructions on ember-cli 1.13.9 but when rest api server is not accessible I am receiving following errors:
Got error for dynamic url, try to pull from cache: TypeError: Failed to fetch at TypeError (native)
The FetchEvent for "http://localhost:4000/v1/clients" resulted in a network error response: an object that was not a Response was passed to respondWith().
The text was updated successfully, but these errors were encountered: