ODrive
ODrive copied to clipboard
liberodark
[BUG] Insecure Browser
Describe the bug Google shows an unsuported browser prompt after attempting to setup an account.
To Reproduce Steps to reproduce the behavior:
- Start the app
- Setup an account
- When the Google login screen shows, input a valid email The login page would then show an "insecure browser" message
Expected behavior User can login normally.
Screenshots [https://live.staticflickr.com/65535/50236617351_99a2001095_z.jpg](insecure browser)
Desktop (please complete the following information):
- OS: Ubuntu 20.04 LTS
- Version 0.2.2
This browser or app may not be secure. Learn more
Try using a different browser. If you’re already using a supported browser, you can refresh your screen and try again to sign in.
I can confirm this bug
I also have the same problem Pop os 20.04 LTS via Flatpak Pop os 20.10 via Flatpak
Me too, I'm having the same issue.
Windows 10 Pro:
Running latest version 0.2.1 of ODrive.
Same error as the OP.
I may have disabled edge/microsoft explorer updates.
I also have the same problem with free gmail account, even enabling access by insecure applications in Google account. I installed Odrive v0.2.1 and v0.3.0 with .deb file in Xubuntu 18.04 x64
Message:
This browser or the app may not be secure. Please try a different browser. If you use a compatible browser, refresh the page and sign in again.
When I used my institutional email, based in Google, entry, but not syncronize.
Encontrei o mesmo problema aqui no ubuntu 20.04. Vamos analisar o source para ajudar na resolução desse problema.
Also have the same issue. Anyone gonna fix this? (@liberodark )
Debian 10, may be something to do with 2FA
I was able to get it working by cloning distro and running locally (run npm run release-linux ). I was actually trying to get this fixed, but it seems that adding account in localy bundled app just works without problem. It's shame tho, because I cannot prove if my solution works. Anyone willing to collaborate?
Happy to help if I can: I'm not a developer and Windows only but if you have a method or other procedure to test then by all means.
maybe help
Information for app developers
If you implemented "Sign in with Google" with the Chromium Embedded Framework, you’ll need to migrate to a more secure alternative:
Switch to use browser-based OAuth. Migrate your desktop app to a Progressive Web App.
Same here!
elementary OS 5.1.7 Hera, built on Ubuntu 18.04.4 LTS.
I tried with ODrive installed as DEB (0.2.1), AppImage (0.2.1) and Snap (odrive and odrive-unofficial). None worked.
Same problem and nothing solution 5 moth after, and the problem its google, because same problem in other apps in windows (super productivity), but the problem right now its nothing fix
Well, as it's written on the ReadMe: Recommend to use VGrive as alternative of this app.
MXLinux this is my problem as well, it obviously started on 3/20/21 as that was the last sync time. I tried uninstalling and reinstalling, clearing browser cache nothing seems to fix this issue,
I'd suggest closing this issue since there doesn't seem to be much progress being made; only just other people complaining that it won't work (thanks to restrictions imposed on Google which are hard to get around on our side without a rewrite of the auth system).
It seems that the owner of this repo is pushing for us to use an alternative since this repo isn't really in active development any more, and I doubt that there are going to be any fixes issued in the near future.
(I'm not a maintainer of this repo btw, before anyone asks!)
That stinks, but understandable, it was a really good app, been using for a really long time. Sorry to see it go.
@Bradford1040 Yeah, it's a shame! Haven't tested VGrive, but it seems to be the way to go. According to the readme of this repo:
Recommend to use VGrive as alternative of this app : https://github.com/bcedu/VGrive/
VGrive looks to be just as good as this, though personally I do think it has a bit of a strange name!
