-
Notifications
You must be signed in to change notification settings - Fork 393
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
Navigation Timeout Exceeded #131
Comments
Can be related puppeteer/puppeteer#1908, peterbe/minimalcss#112 |
What version of |
Rolling back to |
In |
Having the same issue here, but with no effect when rolled back to |
@gopchi do you have some third-party resources? Can you try to create reproducible example? DId you tried |
@stereobooster doing what you said worked, but now in the postbuild process there is an error saying Unhandled Promise rejection... for some routes. Despite that it builds the routes and they work. |
@gopchi can you copy/paste error message. It can happen that those notifications are from your application, not from |
@stereobooster There it is:
It happens on different route every time I try to build. Sometimes they are all ok except the last one. Other times 4 of the routes get this error. Using node v8.9.4 |
@gopchi this sounds like an issue in puppeteer and not the same as described in this ticket. You can try create reproducible demo and open ticket here or in puppeteer issue tracker. If you open ticket here I will try to investigate and eventually will open ticket in puppeteer issue tracker. |
@stereobooster Okay, thanks I will open a new issue on this error. |
Closed in favour of #240 |
I'm getting
Error: Navigation Timeout Exceeded: 30000ms exceeded
when running react-snap locally. It renders all the top-level pages as expected, and then when it hits the first detail-view URL it throws the error.It wasn't doing this before and I haven't changed any code in the component, although the page itself is new, as new items have been added to the CMS and are now being pulled from the API. I have tried removing the offending item and running build again, but the same error happens when it gets to the first detail-view URL again (even though it's a different item).
Error log pasted below:
The text was updated successfully, but these errors were encountered: