Samsung Galaxy S7 Edge (SM-G935U)
Plan: My Choice + 1 GB
After searching Republic Community, I’ve found that my problem has been festering for years with no end in sight. Frustrating, since it’s clearly a lack of app developers’ interest in making what are (in Twitter’s case at least) very simple changes. INDUSTRY & REGULATORY PRESSURE might force a fix by FCC and/or app developers. How about it guys? ATT offers a VOIP option - wouldn’t they make a powerful ally??
I was using Twitter without problems until early June, when I edited my account’s screen name.
The next time I used Twitter, I got a message saying the account was “limited” or “suspended” due to unusual activity.
I couldn’t log in to Twitter. When I tried, the home page was covered by a pop-up dialog asking me to verify my phone by accepting a SMS text and entering the code. When I tapped to proceed, Twitter responded: “Sorry, this carrier is currently not supported.”
A support robot message from help.twitter.com suggested changing my password, which I did successfully. However, this made no difference in the problem. Verify attempts still get the response “Sorry, this carrier is currently not supported.”
The likely explanation is that my phone provider, republicwireless.com, uses a hybrid WiFi VOIP / cellular algorithm to route phone calls and texts. If an online app’s server queries the phone number’s connection type, it shows up as “wireline” or “landline” rather than “wireless”. The server at this point may erroneously conclude the connection is a traditional land line, incapable of supporting SMS and MMS messaging.
My hybrid phone has had no problems for years using standard SMS and MMS messaging apps, as well as Twitter. I suspect that my profile edit kicked in a security check (a good thing) that invoked bad code which failed to recognize my phone number’s support for SMS (a bad thing).
Republic’s help forums are littered with complaints about failures on the part of certain online apps, including Twitter and Venmo, to recognize SMS support.
The problem is compounded by the difficulty of getting someone at Twitter to pay attention to it. It’s easy enough to open a ticket, but Twitter subsequently closes the ticket and takes no action on it.
Given that its business model is based on hybrid telephony, Republic (and other providers of VOIP over mobile phones) can hardly be expected to just drop VOIP functionality. Forcing platform apps like Twitter to fix this (if my analysis is correct) simple bug may require a combination of public, corporate, and regulatory action. Republic can play a leading role in this if it chooses to. Seems like a no-brainer to me.