Number registration (for push messaging) doesn't work with Google Voice

[csoghoian]

The new push based TextSecure doesn't seem to like using Google Voice numbers (which are then forwarded to my phone's real number via SMS).

• Although there are of course privacy downsides associated with letting Google see all of your incoming/outgoing SMS data, there are also serious privacy harms associated with letting people know your actual phone number, rather than a number that will just forward texts to you*

The first step of the TextSecure number registration process ("Connecting") works fine. An incoming text message with the verification code is received by the default Android SMS app, but TextSecure doesn't catch it.

Thankfully, after 2 minutes of waiting, I am given the opportunity verify by voice, which does work.

[TheBlueMatt]

If you're on CM, voice+ works, but...yes, this should be fixed outside of requiring CM.

[yonkeltron]

I can confirm that TS does not currently work with Google Voice on my Samsung Galaxy S4 on Verizon. Would love to see this implemented.

[yonkeltron]

I can confirm that Google Voice registration does not work on my Samsung Galaxy S4 (Verizon).

[generalmanager]

The FAQ says it works if you wait for the timeout and try voice activation:
http://support.whispersystems.org/customer/portal/articles/1468990-how-can-i-get-textsecure-working-with-my-google-voice-number-
Does this work for you? Maybe we should inform users that they should use voice registration with google voice.
Do you know if there is a simple way to filter numbers and automatically do voice activation if somebody enters a google voice number. Does Google have a fixed address space or something?

Edit: looks like there is no publicly known list/address space for GV: http://www.crimetime.com/identification-of-google-voice-numbers.htm
So we're probably down to showing people the voice option from the beginning, with the information that SMS will not work with all GV.

[yonkeltron]

Yeah, I waited for the timeout and requested a voice call but it never came. Bummer.

Ninja edit: The call does come sometimes but TextSecure displays a "Network Error" message when I try to verify.

[deutrino]

I use an Android device with no cellular data service, and I use Google Voice for SMS (via Google Voice over wifi) to other mobiles while using it. When installing TextSecure, I had to verify my Google Voice number with a phone call (which I answered on one of my other phones - Google Voice forwards to them all) after waiting for 2 minutes - even though the SMS came to the device on which I was installing TextSecure via Google Voice!

For Android, at any rate, I imagine maybe one could detect the presence of Google Voice (and then maybe intercept inbound texts from it, since they're not true SMS). But probably the least-work option here is to have the user select voice or sms auth, and be able to abort the 2-minute countdown if they selected sms auth, which takes them back to the select dialog.

[andreimarcu]

This is still an ongoing issue and pretty annoying.
You're sending a 6-number code via text, and I receive it, so let me manually input it, like most other messaging apps do.

[deutrino]

That would be an easy workaround. "Having problems? Input the code manually"

[patcon]

Just to put it on the radar, it's less and less just a Google Voice phenomenon. There are an increasing number of MVNOs offering easy SIP numbers and special texting apps:

• http://www.touch.com/
• http://www.freedompop.com/

These companies mainly offer their own devices, but let you show up with your own device, which may be wifi only.

Also, not to mention Hushed app, which isn't an MVNO, but allows wifi-only devices to act as phones.

[rhodey]

this is working for me now on Nexus 5 w/ stock Lollipop 5.1 & TextSecure 2.10.2. anyone still experiencing this issue and on what device, build, etc?

[deutrino]

• Do I need to reinstall to find out?
• Has work gone into fixing this? IIRC, last I registered, the app told me Google Voice wouldn't work.

[rhodey]

@gordon-morehouse when registering, enter your google voice number-- you should receive an SMS verification code, if that does not arrive you will receive a phone call where the code will be read to you. I've been using a google voice number on my test device for months, let me know if this doesn't work for registration and I will reopen.

[deutrino]

Zero offense intended, but that didn't really answer either of my questions.

I don't see any way to re-register in the app UI. I would like to test this, but not at the expense of blowing away my key, my history, etc. I am already using TextSecure registered to my carrier number on my only device, because it refused to work with Google Voice.

This is quite an old version of Android (2.3.4). If it's not worth testing on such an old version, I'd rather not go through the pain of reinstalling to test until I next wipe the device.

[rhodey]

thanks for the clarification, sorry I didn't understand your original post. you can re-register with a different number by going to Settings > Advanced > TextSecure messages, toggle this option and your current number will be unregistered then you will be prompted again to register with a different number.

[moxie0]

This will mess up your existing sessions if you change your number, though.

[eligrey]

Why isn't there an option to manually enter the text verification code, for users of Google Voice? It seems unnecessary to have to wait 2 minutes to enter a code that you already received immediately.

[lommaj]

I have the same issues, cant register with google voice. I get the reg code via sms but the signal app doesnt pick it up.

With the call option im not getting a call.

[ghost]

@moxie0 Couldn't you export your "chat", change your number, and import the "chat"? Would that work?

[Consequences]

Having the same issue with Google Fi phone. Tried the verification via SMS message, and then also the voice verification. SMS times out and even when I get the voice call/code when I input it I get "Network error!"