-
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
TimeoutError: Navigation Timeout Exceeded: 30000ms exceeded #541
Comments
Exactly the same problem. Any solution? |
Same problem. Ay solution? I'm using react-snap 1.23.0 |
Same problem. react-snap 1.23.0 |
Same problem on react-snap 1.23.0. I'd checked before thread, this problem is related to firebase and puppeteer. My case downgrade react-snap 1.10.0 works well. |
I was able to fix this by setting Puppeteer options to "waitUntil": "networkidle2" |
Same issue, none of the above methods worked for me. |
Just add puppeteer.timeout with a greater value wich works for you and also skipThirdPartyRequests in reactSnap: "scripts": { |
I am experiencing this issue as well, and the above solutions did not work. |
for future refrences hope y'all found a solution but on my end degraded to version @1.10.0 npm install [email protected] --save-dev this what worked for me |
?? error at / TimeoutError: Navigation Timeout Exceeded: 30000ms exceeded
at D:\OfficiaL\blog\client\node_modules\puppeteer\lib\LifecycleWatcher.js:142:21
-- ASYNC --
at Frame. (D:\OfficiaL\blog\client\node_modules\puppeteer\lib\helper.js:111:15)
at Page.goto (D:\OfficiaL\blog\client\node_modules\puppeteer\lib\Page.js:674:49)
at Page. (D:\OfficiaL\blog\client\node_modules\puppeteer\lib\helper.js:112:23)
at fetchPage (D:\OfficiaL\blog\client\node_modules\react-snap\src\puppeteer_utils.js:232:22)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] postbuild:
react-snap
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] postbuild script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Admin\AppData\Roaming\npm-cache_logs\2021-08-21T21_02_16_602Z-debug.log
this one is updated version still not working
The text was updated successfully, but these errors were encountered: