mirror of
https://github.com/Llewellynvdm/nativefier.git
synced 2024-12-23 10:38:55 +00:00
ec0ea4bd67
Per #1112, I'm adding some common troubleshooting steps to the README. As well, this adds a checkbox requesting users to check this section before submitting a ticket, which will hopefully lead to more self-help.
1.7 KiB
1.7 KiB
| name | about | labels |
|---|---|---|
| Bug report | Report something broken | bug |
Homework
- I looked at
nativefier --helpand https://github.com/nativefier/nativefier/blob/master/docs/api.md - I checked the Troubleshooting section of the README.
- I searched existing issues, open & closed. Yes, my bug is new.
- I'm using the latest version available at https://github.com/nativefier/nativefier/releases
Bug description
A clear and concise description of what the bug is.
Steps to reproduce
Give your full nativefier command and its logs, with the --verbose flag, on a public site:
nativefier --verbose --some-option https://mysite.com
<paste your verbose build logs too>
Expected behavior
What you expected to happen.
Actual behavior
What happened instead.
Debug info
- Console logs of your
nativefierbuild command, with--verboseflag - If the bug happens at app run time, the in-app DevTools console logs (open it with F12)
- Error messages
- Screenshots
- Anything else relevant!
Context
- Nativefier: (for example: 9.1.0)
- Node.js: (for example: 14.6.0)
- Npm: (for example: 6.14.7)
- OS: (for example: Windows 10 build 1809)
- Is it a regression? If yes, what's the last working / first broken version?
- Additional context: (for example: "I'm behind a proxy, with configuration X and protocol Y")