You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I signed up for a testing OkCupid account last week to test an unrelated-to-relay Firefox bug, and in the process, I discovered that I was unable to use my relay phone number as part of OkCupid's (mandatory) phone-number-verification SMS-confirmation-token flow.
Possibly they're detecting that Relay phone numbers are "synthetic" in some sense and refusing to send an auth token to them?
Follow the prompts: enter a username, password; first-name, birth date, zip code, gender, photo, etc. (At some stage you have to answer personality questions too; I can't remember if that happens now or later.)
Eventually, OkCupid asks you for a phone number. Enter a Firefox Relay phone number.
OkCupid will tell you that it sent a sms to that phone number. Watch for that SMS. If you don''t see it, try to click the button to send it again.
I tried requesting an SMS to my relay phone number via a different web service and that one made it through just fine.
I eventually relented and gave OkCupid my actual cell number, and they texted an auth code to that number just fine (it reached my actual phone and showed up on the relay web-dashboard).
So presumably OkCupid (or their 3rd-party auth-code-sending service) is detecting Relay phone numbers as being untrustworthy/unsuitable-to-send-auth-codes-to somehow. (Maybe because of however we're virtualizing the phone number, through VOIP or whatever?)
The text was updated successfully, but these errors were encountered:
I hit the same issue for BlueSky ( https://bsky.app/ ) which is now open for sign-up, no invite code needed.
The last stage of the BlueSky sign-up process requires a phone number, to which they text an auth code. I put in my Relay phone number, but never received the auth code on my phone or relay-web-dashboard. I went back and put in my real cell number, and the auth code arrived immediately.
I signed up for a testing OkCupid account last week to test an unrelated-to-relay Firefox bug, and in the process, I discovered that I was unable to use my relay phone number as part of OkCupid's (mandatory) phone-number-verification SMS-confirmation-token flow.
Possibly they're detecting that Relay phone numbers are "synthetic" in some sense and refusing to send an auth token to them?
My steps were roughly:
EXPECTED RESULTS:
SMS should arrive.
ACTUAL RESULTS:
The SMS never arrives, nor does it show up on the https://relay.firefox.com/phone/ web-dashboard.
Notes:
The text was updated successfully, but these errors were encountered: