Skip to content
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

Clicking "yes" on update window doesn't open download link #2363

Closed
mgrandi opened this issue Jan 25, 2020 · 7 comments
Closed

Clicking "yes" on update window doesn't open download link #2363

mgrandi opened this issue Jan 25, 2020 · 7 comments
Labels
bug It's a bug

Comments

@mgrandi
Copy link

mgrandi commented Jan 25, 2020

I noticed when trying to download the latest joplin update (1.0.179) after i restarted my computer, is that the download link when you click "yes" on the auto update window doesn't actually open the download link

Environment

Joplin version: 1.0.178
Platform: win32
OS specifcs: windows 10
browser: firefox 72.0.2 (64-bit)

Steps To Reproduce

  1. make sure browser is open
  2. open joplin, or if it is already running go to help -> check for update
  3. click "yes" to update
  4. the browser does not open to go to the joplin download link

Describe what you expected to happen:

the browser should go to the joplin download link

Logfile

the log file doesn't have anything relevant

EDIT: i thought this was because the browser was closed, but then i tried it with the browser being open, it also doesn't work

@mgrandi mgrandi added the bug It's a bug label Jan 25, 2020
@mgrandi mgrandi changed the title Clicking "yes" on update window doesn't open link if browser is closed Clicking "yes" on update window doesn't open download link Jan 25, 2020
@bedwardly-down
Copy link
Contributor

bedwardly-down commented Jan 25, 2020

It would still be a good idea to have a logfile, even if it doesn't seem relevant. There may be something the devs know that you don't about what the logs say that could be affecting you.

Also, do you have an antivirus / firewall installed that could be blocking Joplin from working? Have you tried launching Joplin from Powershell / Cmd Prompt so that you can get an idea of what's happening when you click that button? If you can paste what is said there here, that could definitely be useful for finding out what's up with Joplin on your end.

I'm not on Windows, so I can't directly try out any fixes but can definitely steer you in the right direction.

@dpoulton-github
Copy link

dpoulton-github commented Jan 25, 2020

Joplin version: 1.0.178
Platform: Windows 10 x64 (1909)

Same here. Had to go to the Joplin web-site to download the package.

EDIT: I meant the Joplin Github site!

@ssnellings
Copy link

Joplin version: 1.0.178
Platform: Windows 7 x64

Same issue with it not working through the app. When I go to the joplinapp.org website manually the windows link points to the following link so I didn't download it since it's the version I'm currently on:
https://github.com/laurent22/joplin/releases/download/v1.0.178/Joplin-Setup-1.0.178.exe

I can see 1.0.179 in the releases section of github, it just isn't working through the app itself and the joplinapp.org link is a version behind. No big deal, I'll just grab it from the releases section.

Great program, thanks for all the hard work!

@mgrandi
Copy link
Author

mgrandi commented Jan 26, 2020

here are my logs, i edited flags.txt to have --logLevel debug and then moved my old logs to a different folder, then restarted joplin, and clicked 'yes' to to the auto update prompt

log-clipper.txt
log.txt
log-autoupdater.txt

@bedwardly-down
Copy link
Contributor

bedwardly-down commented Jan 26, 2020

@mgrandi This issue appears on Artix Linux, too, with nothing showing in the terminal or in my logs about it, either. It's not just a Windows issue. I just attempted with running v1.0.178 AppImage and got the exact same results as you and everyone else.

@bedwardly-down
Copy link
Contributor

Looks like this bug's been fixed in v1.0.179. The update message box fix in its changelog is just this

@tessus
Copy link
Collaborator

tessus commented Jan 27, 2020

yep, fixed via 5c54b83

@tessus tessus closed this as completed Jan 27, 2020
@lock lock bot locked and limited conversation to collaborators Feb 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug It's a bug
Projects
None yet
Development

No branches or pull requests

5 participants