Google Fi support

[jeffcasavant]

I am a Google Fi user. With Google Fi, you can choose either to use RCS ("chat features") or to be able to handle calls and voicemail from the web interface. I chose the latter option, so I'm directed to log in to messages.google.com directly with my Google account rather than to pair the web interface via the QR code. I don't think I have the ability to pair via QR code at all.

This may still be true for Google Fi with RCS turned on, but based on those docs it seems like the QR code flow might work in that case. I can only speak to the non-RCS case.

I'd love to be able to use this bridge while retaining the ability to make and receive calls via Google's Messages for Web interface. It's been years since Hangouts contained my SMS messages, and it'd be nice to have a single place - Matrix - for all my messages again.

[jeffcasavant]

Based on further conversations with Fi users, I do have the ability to log in via QR code, and can turn on RCS. As mentioned I will lose the web-based call and voicemail functionality. I went ahead and did this, and the bridge works great!

I'd still like to be able to log in with my Google account, though, eventually.

Just following up in case another Fi user finds this issue.

[DRSchlaubi]

Now that Google switches to account-based login for regular users, this gets more relevant, since they can't log in via qr code

[tulir]

Everyone can switch back to QR code login (but may need to unlink existing devices if you already linked some via google login)

[DRSchlaubi]

Whilst true, it would still be better to have support for Google Account log-in, if that's possible, it could probably work similarly to the Discord login

[kubo6472]

I have a question, is this the same as support for "switch to google account login"?

[rom4ster]

Word is this is going to be rolling out as the only option, this should be marked as an urgent priority as if this is true, its breaking.
https://www.reddit.com/r/beeper/comments/19fag6h/comment/kjmfite/?utm_source=reddit&utm_medium=web2x&context=3

This is the source I have.

This should be urgent as it affects not only core functionality but the ability to even use the app in any form for users.

Also this should probably be a bug at this point.