Windows - Can't Log In - Next from Email Does Nothing

[KaliMau]

Describe the bug
New install - when trying to log in to my google account, I can enter my email or phone number, but the "next" button seems to reload the box and doesn't advance to password or other credentials.

New
To Reproduce
Steps to reproduce the behavior:

1. Access program
2. Click on 'sign in'
3. Enter your email or phone
4. Click 'next'

Expected behavior
Expect clicking next to advance the sign in credentials to password

Screenshots
Gyazo video:
https://gyazo.com/791dcd920156aa3b4f4a1e8446b0c195

Desktop (please complete the following information):

• OS: Window 11 Pro / 64
• Version [e.g. 22]

Additional context

If you have Google Fi, you dead end and have to abandon the program since you can't use QR code.

[breichart]

This is a known issue. You have to use the QR code form your messages "Device Pairing" section. Not sure when this will get fixed, as I have to do the QR code after "Installing updates" every day.

[KaliMau]

Thanks for the response.
I have a google phone and am using google Fi, so there's no option for me to use the QR code. I tried that but my phone tells me I don't need it.

[IGS-GIT]

In order to use QR scanning, you have to unpair from your other devices .
In messages on your phone, tap on your profile and go to device pairing. There should be an option to unpair all devices. After this, go to the same setting and select QR Pairing

[breichart]

In order to use QR scanning, you have to unpair from your other devices . In messages on your phone, tap on your profile and go to device pairing. There should be an option to unpair all devices. After this, go to the same setting and select QR Pairing

I did that. It's only on one device and same issue. I have to "Check for updates", then "Install updates", then fully re-install, and rescan the QR code around every other day. It's very annoying.

[Drexl]

I also can't sign in or use QR codes using a google phone and google fi. This is what the device pairing page looks like.

[IGS-GIT]

I also can't sign in or use QR codes using a google phone and google fi. This is what the device pairing page looks like.

You need to disable "Google Fi Wireless settings" in the advanced tab. This also disables RCS chats, so this shouldn't be on to begin with. Disable that and it should bring back QR scanning

[Drexl]

RCS chat settings are in a different menu, and are already off. Google fi wireless settings only contains the option to sync my chats across devices, which is a big deal and I definitely want that to stay. Is there no other way?

[BrockObamaFB]

I have very limited development experience, however, after a bit of testing, I figured out that this has to do with Electron being the user agent.

I downloaded the source code, modified the user-agent line to read:

            "User-Agent": mainWindow.webContents.userAgent.replace(
              "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36 GLS/100.10.9939.100",
              ""

instead and I was able to login and use new features that I previously wasn't able to use before. I also have the ability to instantly see updates and don't have to wait for my phone to sync with my desktop. I can also use RCS as well.

I would suggest downloading the source code and modifying the "src\background.ts" file with the above since the developer of this application has gone missing and/or updates very seldomly.

[OrangeDrangon]

Release coming today.

[BrockObamaFB]

I'm still seeing the error, unfortunately. :(

Edit: I did delete local and roaming AppData for Android Messages before attempting and it still gives me this error.

[OrangeDrangon]

I will take another look. QR sign in worked on two platforms before I pushed the release but I will try with username login.

[OrangeDrangon]

Yeah username login is still erroring out I will look into when I get a chance I guess.

[StormySky16]

Yeah username login is still erroring out I will look into when I get a chance I guess.

I believe I've mentioned it before, but due to a new PC issue I've had to reinstall the app and ran into this issue again: Previous versions of the app work fine with username login, specifically v5.5.0. Hopefully that helps you narrow down the issue.