-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Google blocks login from nativefier app, unless setting userAgent to non-Chrome browser #831
Comments
this is a well known issue: Google will no longer allow OAuth requests to Google in embedded browsers. "On April 20, 2017, we will start blocking OAuth requests using web-views for all OAuth clients on platforms where viable alternatives exist." We received this notice. In our iOS app using the Google drive, but google drive sdk no updated. |
Google solutions: https://developers.google.com/identity/protocols/OAuth2InstalledApp |
you cannot electronize Google's original apps anymore -> deal with it, it's forbidden |
Weird, it still works fine for me. |
It works for me on installations that I had logged into previously, but not newly created applications. |
I can do it on new applications |
@Aidoboy are you using 2-factor authentication? Further testing seems to confirm that the issue only occurs with 2-factor authentication enabled on the Google account. If this is in fact the limitation, I wonder if there are any practical workarounds besides completely disabling 2-factor authentication? |
it's not 2FA related any app trying to reach out to Google OAuth login page will open an external browser window
|
It's working for me with 2FA
…On Tue, Sep 3, 2019, 3:13 AM Filip Oščádal ***@***.***> wrote:
it's not 2FA related
*any app trying to reach out to Google OAuth login page will open an
external browser window*
installed apps must open the system browser and supply a local redirect
URI to handle responses from Google's authorization server
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#831>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABYT6YRPQHMPE7TOHF2FL5TQHYMCDANCNFSM4IMNW2VQ>
.
|
It's working with 2FA for me too. I use |
This must have been a temporary issue on the Google end, as I just tried the original nativefier app recently, and it's logging in just fine now. |
https://security.googleblog.com/2019/04/better-protection-against-man-in-middle.html note:
|
this works perfectly |
@maxogden App crashes when trying to use --electron-version 7.1.2 (osx Mojave) |
@thehunmonkgroup and everybody else - I found a fix by this comment ( thank you so much @futurehaskins). This works well: |
Doesn't work for me, unfortunately |
Did to no the error in my message? There is a space before ".google".
Remove it and try.
…On Wed, Dec 18, 2019, 10:14 PM Daniel G. Wilson ***@***.***> wrote:
@thehunmonkgroup <https://github.com/thehunmonkgroup> and everybody else
- I found a fix by this comment
<https://github.com/ramboxapp/community-edition/issues/2495#issuecomment-562358578>
( thank you so much @futurehaskins <https://github.com/futurehaskins>).
This works well:
nativefier https://mail.google.com/mail --user-agent 'Mozilla/5.0 (X11;
Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0' --name "My
Gmail" --internal-urls ".*accounts .google.com.*"
Doesn't work for me, unfortunately
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#831>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQPXCPPDGX76IJ65I4FH3DQZKACFANCNFSM4IMNW2VQ>
.
|
Finally found a solution, thanks royts. Removing the space worked for me. Kept getting the 'This browser or app may not be secure' when trying to sign into googles remote desktop. |
Tried again without the space (could have sworn I tried that previously, hmmm) and it works perfectly. |
This isn't working currently.
Here is the address from the tab:
|
Here is the command that worked for me:
I copied it from here: https://aur.archlinux.org/packages/google-calendar-nativefier/ |
Hope this little tidbit also helps people out: After successfully logging in using the FF userAgent hack described, I found that external links were broken in Gmail. Solved this by:
|
Closing for now. If this continues to be an issue we could reopen. 😊 |
After a bit of tirlas and errors, I think it has to do with the domain. Accounts with |
Thanks. This was the only way I was able to log into YouTube (I just removed the "music" references to create a YouTube web app). |
Just to add to this solution (which worked for me as well): in order to open external (non-google) urls directly in the default browser, in point 4. also change the part |
Looks like this is back, and this time there's no workaround. See this post by Google: https://support.google.com/accounts/answer/6010255 |
@mobusby can't repro. Here, the recipe documented in CATALOG / Google Apps, |
Well, that's interesting. |
Sure. Just pushed a few README commits to make it more visible.
Hmmmmmmm, can't repro here, for me both work fine. The contrary would have been very strange; when you omit the protocol, Nativefier automatically fills it as https. That being said, I do believe you that sometimes somehow you aren't able to login, and it matches the new May 30 deadline for strengthened Google Login annoyance. But the conditions to be annoyed and to evade it seem to be unclear. |
*nativefier* is not considered as *secure* for Google, not possible to
containerize Google Web Apps
Filip Oščádal 🍀📱
…On Tue, Jun 21, 2022, 11:56 Matt Sephton ***@***.***> wrote:
Neither work for me.
nativefier sheets.google.com --user-agent safari
gets
[image: Screen shot 2022-06-21 at 10 55 09]
<https://user-images.githubusercontent.com/49612/174772507-543fcd90-bfc5-4cbc-835b-8a628f34e226.png>
—
Reply to this email directly, view it on GitHub
<#831 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAASMXULNPPGY4QRA5XXTJTVQGGU5ANCNFSM4IMNW2VQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I did get it working, so 🤷 |
how? 🤔
Filip Oščádal 🍀📱
…On Tue, Jun 21, 2022, 16:16 Matt Sephton ***@***.***> wrote:
I did get it working, so 🤷
—
Reply to this email directly, view it on GitHub
<#831 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAASMXW2TT6BZE74ISHFZQLVQHFDJANCNFSM4IMNW2VQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
as found on Stack:
*Warning:* This answer relies on changing the browser's user-agent. As of
Jan. 2021, Google disapproves of this and warns not to do this (see EDIT4).
Use at your own risk!
Filip Oščádal 🍀📱
…On Tue, Jun 21, 2022, 16:16 Matt Sephton ***@***.***> wrote:
I did get it working, so 🤷
—
Reply to this email directly, view it on GitHub
<#831 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAASMXW2TT6BZE74ISHFZQLVQHFDJANCNFSM4IMNW2VQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
See above #831 (comment) |
This seemed to work fine for me today:
|
specified here:
https://github.com/nativefier/nativefier/releases/tag/v43.0.0
Filip Oščádal 🍀📱
…On Fri, Jul 1, 2022, 20:27 Daniel Bachhuber ***@***.***> wrote:
This seemed to work fine for me today:
nativefier https://mail.google.com --icon ~/Documents/Icons/gmail-mac.png --strict-internal-urls
—
Reply to this email directly, view it on GitHub
<#831 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAASMXWLXBTT2KUANXMRKDTVR4Z7TANCNFSM4IMNW2VQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Another example that is working, this time for Google Fi:
2-Factor enabled, on VPN, from the US, verification via a tap on the phone. Turns out all you got to do is be honest :D |
Just redoing mine so they are arm64 and can confirm the above |
…g userAgent (nativefier#1174) When a new child window is spawned (such as for a Google login popup), those child windows were not receiving the mainWindow's properties. Chiefly among this was the userAgent which caused a bug in nativefier#831
|
|
i tried all of the abve commands but i cannot login using gmail |
never mind i tried again and this one worked for me: |
Thanks man, that worked! :) |
Thanks that worked ! |
EDIT from maintainer @ronjouch see comments below, the workaround as of March 2020 is to lie about the userAgent, for example passing
--user-agent "Mozilla/5.0 (Windows NT 10.0; rv:74.0) Gecko/20100101 Firefox/74.0"
. It would be cool to do that automatically on opening / navigating to anaccounts.google.com
page, PR welcome.Description
I've created a nativefier app for https://contacts.google.com, and it installs just fine, but Google seems to be blocking the initial login with this message:
My older nativefier apps pointed to Google services are still loading OK, I'm guessing because the login is already saved and Google isn't blocking things at that stage.
I'll note that I also tried another desktop app generator (https://github.com/quanglam2807/webcatalog), and the same issue is occurring, so perhaps there's some deeper fix needed at the Electron level or something?
Steps to reproduce issue
Details
nativefier --help
to see if an existing option could fit your needs? Yesnativefier --electron-version 6.0.2 --name "Google Contacts" --icon "/home/hunmonk/Pictures/icons/google-contacts.png" --internal-urls "contacts.google.*?" --single-instance "https://contacts.google.com"
nativefier --version
):v7.6.12
node --version
):v10.15.2
Ubuntu 19.04
The text was updated successfully, but these errors were encountered: