We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
$ (date; LOG_LEVEL=debug ./notes-nc-0.3.0.AppImage) Wed 02 Mar 2022 12:37:16 AEDT 12:37:29.338 › Notes booting 12:37:30.084 › Config directory: /home/mscharley/.config/notes-nc 12:37:30.084 › Log directory: /home/mscharley/.config/notes-nc/logs 12:37:30.084 › Registering schemes as privileged: [ 'app', 'editor' ] 12:37:35.598 › Registering the app:// scheme. 12:37:38.313 › Registering the editor:// scheme. 12:37:38.314 › Checking for update 12:37:50.299 › Update for version 0.3.0 is not available (latest version: 0.2.1, downgrade is disallowed). 12:37:51.935 › Injecting React into page.
Seems like the root cause is electron-userland/electron-builder#6678.
The text was updated successfully, but these errors were encountered:
Compare with running the unpacked linux build:
$ (date; LOG_LEVEL=debug ./linux-unpacked/@mscharleynotes-nc) Wed 02 Mar 2022 12:39:58 AEDT 12:39:58.502 › Notes booting 12:39:58.566 › Config directory: /home/mscharley/.config/notes-nc 12:39:58.566 › Log directory: /home/mscharley/.config/notes-nc/logs 12:39:58.566 › Registering schemes as privileged: [ 'app', 'editor' ] 12:39:58.664 › Registering the app:// scheme. 12:39:58.668 › Registering the editor:// scheme. 12:39:58.669 › Checking for update 12:39:58.675 › Error: Error: ENOENT: no such file or directory, open '/home/mscharley/Code/mscharley/notes-nc/dist/linux-unpacked/resources/app-update.yml' 12:39:58.851 › Injecting React into page.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Seems like the root cause is electron-userland/electron-builder#6678.
The text was updated successfully, but these errors were encountered: