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

Unable to download from Firefox 63.0.3 and Chrome 70.0 #250

Closed
luzb3l opened this issue Nov 20, 2018 · 7 comments
Closed

Unable to download from Firefox 63.0.3 and Chrome 70.0 #250

luzb3l opened this issue Nov 20, 2018 · 7 comments

Comments

@luzb3l
Copy link

luzb3l commented Nov 20, 2018

Both browsers cancel the download automatically and mark it as dangerous.
Is there a way around this? Is this a known issue?

@ErikBjare
Copy link
Member

Woah, we've never heard about this before. Which platform are you using/trying to download?

@luzb3l
Copy link
Author

luzb3l commented Nov 20, 2018

It's Windows 10 Enterprise 64bits.

This is Firefox 63.0.3

2018-11-20 17_09_21-releases activitywatch_activitywatch

This is Chrome 70.0

2018-11-20 17_10_33-releases activitywatch_activitywatch github

I specified in Firefox to "Allow the Download", and when I scanned it with Windows Defender, it gave me this:

2018-11-20 17_15_46-windows defender security center

Let me know if you need anything else to reproduce it.

@ErikBjare
Copy link
Member

ErikBjare commented Nov 26, 2018

Related to #181 and #140. I don't really know what to do about it that would give a reliable result.

Does the same thing happen for v0.8.0b6?

v0.8.0b7 is broken on Windows (see #248) so not much use in using that anyway.

@harvzor
Copy link

harvzor commented Nov 27, 2018

Firefox complained at me for downloading b7 but seemed to download it anyway (as I found it in my downloads folder).

@greysondn
Copy link

Just going to add this snapshot here.

image

Have you considered submitting it to vendors as a potential false positive? Especially if you get a known working build it may be a good idea.

@ErikBjare
Copy link
Member

@greysondn Yes, it's discussed in #181. We encourage users to do so themselves as we (maintainers) would rather spend time on further development and don't really have the time. If someone can let us know of a way to submit false positives automatically, that would of course be considered.

@ErikBjare
Copy link
Member

Closing, further discussion should go in #181.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants