Last week I ported my mobile number from Eastlink to Public Mobile. Everything went well, and I was immediately able to send and receive both calls and SMS.
One problem I encountered, however, was that one-time passwords sent by SMS from shortcodes from sites like Instagram and Twitter were not reaching me; I never had problems with these when I was with Eastlink.
I raised this issue in a private message to @Moderator_Team and they tenaciously pursued the issue over the past week, eventually determining that the upstream SMS service provider that Twitter and Instagram use was continuing to route these messages to Eastlink, my old provider.
The upstream provider was able to update this, and I'm now receiving these messages without issue.
Posting this here in case others experience the same thing when porting a number to Public Mobile from elsewhere.
Also posting here to tip my hat to @Moderator_Team for providing excellent support.
Good to know.
So basically port wasnt completed fully, and portion of the service was unsuccessful.
@ruk Wondering how long does it take to fix it?
Surely this has to be automatic even if it takes a bit of time for information to fan out to the various interconnected systems. Manual intervention would be impractical.
I ported on July 4, 2018 and the issue was resolved today, July 13, 2018.
I didn't raised the issue in a private messages with @Moderator_Team until July 6, 2018, however, so, in the end, it took 4 business days to resolve.
This to me is similar to the problems with FaceTime and iMessage on iOS devices.
in this case, it was switching providers. However, when switching devices from iOS to anything else, one should remember to unsubscribe to the ability to use those features, to prevent such errors.
I'm having this issue with Facebook and also other apps, and it's been more than a couple of days since I moved from Chatr to Public. What gives?
My impression from my own similar experiences, related above, are that somehow, in the thicket of complexity that is the SMS system and mobile operators, something gets cached somewhere -- either at the application level, or somewhere inbetween.
I had to raise this with Public Mobile to get the "cache cleared," but it may have repaired on its own had I been more patient.
The good news is that both Facebook and Twitter allow 2FA/MFA via apps now instead of text messages. Do yourself a favour and switch to using Authy for both.
To add to what @srlawren If you are using Authy with the backup option MAKE SURE YOU TURN OFF the Add New Devices option OFF under Devices section after you have setup all your devices, since Authy needs a cellphone number to authenticate there is still a potential weakness.
For an 2FA authenticator option that doesn't involve cellphone #s AND have a backup option, I recommend the Microsoft Authenticator. The iOS verion stores the backup on your iCloud to keep things seperate. It does do propreitory things like generates 8 digit 2FA vs 6 for Microsoft and AD accounts, however for industry standard 2FA it is solid.