Skip to content
This repository has been archived by the owner on Nov 27, 2022. It is now read-only.

Fix : This browser or app may not be secure #68

Closed
wants to merge 0 commits into from
Closed

Fix : This browser or app may not be secure #68

wants to merge 0 commits into from

Conversation

ghost
Copy link

@ghost ghost commented Feb 17, 2022

macOS (Working):
image

Linux (Working):
image

Windows 7 (Working):
image

@ghost
Copy link
Author

ghost commented Feb 17, 2022

This should fix #52

@ankurk91
Copy link
Owner

We are already overriding user agent

export const userAgentString = `Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:${firefoxVersion}) Gecko/20100101 Firefox/${firefoxVersion}`

We are using Firefox user agent string here.

@ankurk91 ankurk91 changed the title Fix Login Fix : This browser or app may not be secure Feb 17, 2022
@ankurk91 ankurk91 closed this Feb 17, 2022
@ankurk91
Copy link
Owner

I have merged your commits locally, but with Firefox user agent.

But the issue still not fixed for me, i am still getting same error upon login.

@ghost
Copy link
Author

ghost commented Feb 17, 2022

Uh, the user agent I used works for me.
Confirmed on Windows 7, macOS, and Linux.

@ankurk91
Copy link
Owner

Follow these steps:

  • Quit from app completely.
  • Remove the cache folder of this app; for example on Linux
/home/ankur/.config/google-chat-electron
  • Now launch the app, This should be first launch of the app.
  • Enter your personal gmail address (not an organisation one)
  • Notice you wont be able to login now.

Looks like google is also checking several other things not just User Agent. There is no easy way to spoof Google.

@ghost
Copy link
Author

ghost commented Feb 17, 2022

Ah I see the issue. I didn't full test.

@reureya
Copy link

reureya commented Feb 18, 2022

I "resolved" the issue on my end though, I originally came to this thread from Hamsket:

Follow up: I weirdly got it to work now!

I first tried just reloading the tab and then restarting Hamsket a few times, which didn't help. Then I tried clearing the cache and restarting Hamsket, after which I entered the full email address (including @gmail.com, which I don't think I did before).

Not sure what precisely the magic step was, but probably the clearing the cache, restarting Hamsket, and entering the full address procedure taken together (possibly several times) is a tip worth trying.

Repository owner locked and limited conversation to collaborators Feb 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants