Mar 19, 2026 | 2:14 PM EDT
Mar 17, 2026 | 1:59 PM EDT
Mar 17, 2026 | 10:38 AM EDT
Mar 16, 2026 | 5:21 PM EDT
Mar 16, 2026 | 3:21 PM EDT
Mar 12, 2026 | 4:18 PM EDT
Mar 19, 2026 | 2:14 PM EDT
Mar 17, 2026 | 1:59 PM EDT
Mar 17, 2026 | 10:38 AM EDT
Mar 16, 2026 | 5:21 PM EDT
Mar 16, 2026 | 3:21 PM EDT
Mar 12, 2026 | 4:18 PM EDT
Mar 19, 2026 | 6:52 PM EDT
Mar 19, 2026 | 5:46 PM EDT
Mar 19, 2026 | 5:02 PM EDT
Mar 19, 2026 | 4:01 PM EDT
Mar 19, 2026 | 3:20 PM EDT
Mar 19, 2026 | 2:14 PM EDT
Mar 19, 2026 | 3:20 PM EDT
Mar 19, 2026 | 10:36 AM EDT
Mar 18, 2026 | 4:00 PM EDT
Mar 18, 2026 | 10:32 AM EDT
Mar 17, 2026 | 2:41 PM EDT
Mar 16, 2026 | 3:59 PM EDT
Mar 19, 2026 | 5:46 PM EDT
Mar 19, 2026 | 1:14 PM EDT
Mar 19, 2026 | 12:14 PM EDT
Mar 18, 2026 | 5:43 PM EDT
Mar 18, 2026 | 11:25 AM EDT
Mar 13, 2026 | 4:33 PM EDT
Mar 18, 2026 | 1:16 PM EDT
Mar 16, 2026 | 3:21 PM EDT
Mar 12, 2026 | 1:29 PM EDT
Mar 12, 2026 | 11:24 AM EDT
Mar 11, 2026 | 4:23 PM EDT
Mar 9, 2026 | 1:03 PM EDT
Mar 19, 2026 | 6:52 PM EDT
Mar 16, 2026 | 3:03 PM EDT
Mar 10, 2026 | 3:52 PM EDT
Mar 6, 2026 | 4:50 PM EST
Mar 5, 2026 | 4:25 PM EST
Mar 5, 2026 | 4:24 PM EST
Mar 6, 2026 | 3:08 PM EST
Feb 2, 2026 | 12:21 PM EST
Dec 29, 2025 | 1:31 PM EST
Dec 15, 2025 | 2:33 PM EST
Nov 28, 2025 | 10:43 AM EST
Oct 1, 2025 | 9:00 AM EDT
Mar 19, 2026 | 5:02 PM EDT
Mar 17, 2026 | 4:28 PM EDT
Mar 13, 2026 | 3:01 PM EDT
Mar 12, 2026 | 5:56 PM EDT
Mar 2, 2026 | 3:31 PM EST
Feb 25, 2026 | 3:24 PM EST
Mar 16, 2026 | 10:36 AM EDT
Mar 5, 2026 | 4:03 PM EST
Feb 25, 2026 | 4:07 PM EST
Feb 19, 2026 | 1:32 PM EST
Feb 5, 2026 | 1:43 PM EST
Jan 8, 2026 | 10:39 AM EST
Mar 19, 2026 | 4:01 PM EDT
Mar 18, 2026 | 12:12 PM EDT
Mar 13, 2026 | 1:13 PM EDT
Mar 5, 2026 | 3:40 PM EST
Mar 5, 2026 | 12:29 PM EST
Mar 3, 2026 | 4:07 PM EST
Mar 17, 2026 | 3:51 PM EDT
Mar 16, 2026 | 3:59 PM EDT
Mar 11, 2026 | 5:01 PM EDT
Mar 10, 2026 | 2:55 PM EDT
Mar 10, 2026 | 1:54 PM EDT
Mar 6, 2026 | 4:17 PM EST
Mar 17, 2026 | 4:37 PM EDT
Mar 17, 2026 | 11:38 AM EDT
Mar 16, 2026 | 12:56 PM EDT
Mar 16, 2026 | 11:41 AM EDT
Mar 13, 2026 | 3:51 PM EDT
Mar 13, 2026 | 3:27 PM EDT
Mar 19, 2026 | 9:00 AM EDT
Mar 12, 2026 | 6:12 PM EDT
Mar 11, 2026 | 10:56 AM EDT
Mar 10, 2026 | 9:00 AM EDT
Mar 9, 2026 | 9:00 AM EDT
Mar 9, 2026 | 9:00 AM EDT
Mar 19, 2026 | 9:00 AM EDT
Mar 12, 2026 | 6:12 PM EDT
Mar 11, 2026 | 10:56 AM EDT
Mar 9, 2026 | 9:00 AM EDT
Mar 4, 2026 | 12:00 PM EST
Feb 25, 2026 | 1:00 PM EST
Mar 10, 2026 | 9:00 AM EDT
Mar 9, 2026 | 9:00 AM EDT
Feb 27, 2026 | 3:32 PM EST
Jan 27, 2026 | 3:15 PM EST
Jan 6, 2026 | 12:18 PM EST
Nov 26, 2025 | 4:38 PM EST
Feb 13, 2026 | 12:14 PM EST
Nov 28, 2025 | 4:32 PM EST
Sep 17, 2025 | 12:13 PM EDT
Aug 4, 2025 | 10:31 AM EDT
Aug 2, 2025 | 2:32 PM EDT
Jul 26, 2025 | 2:27 PM EDT
Jan 22, 2026 | 4:35 PM EST
Jan 20, 2026 | 3:48 PM EST
Dec 9, 2025 | 2:18 PM EST
Nov 19, 2025 | 3:58 PM EST
Sep 16, 2025 | 2:33 PM EDT
Aug 28, 2025 | 11:32 AM EDT
Feb 24, 2026 | 4:20 PM EST
Feb 23, 2026 | 4:28 PM EST
Feb 19, 2026 | 12:08 PM EST
Feb 13, 2026 | 10:53 AM EST
Jan 16, 2026 | 5:32 PM EST
Dec 16, 2025 | 5:01 PM EST
Mar 5, 2026 | 11:43 AM EST
Mar 5, 2026 | 11:18 AM EST
Mar 3, 2026 | 4:31 PM EST
Feb 25, 2026 | 10:00 AM EST
Feb 11, 2026 | 4:30 PM EST
Jan 21, 2026 | 10:21 AM EST
Jan 20, 2026 | 3:48 PM EST
Aug 22, 2025 | 1:01 PM EDT
Jun 27, 2025 | 8:30 PM EDT
May 21, 2025 | 4:25 PM EDT
Mar 7, 2025 | 2:56 PM EST
Aug 21, 2024 | 1:02 PM EDT
Mar 17, 2026 | 11:38 AM EDT
Mar 13, 2026 | 5:02 PM EDT
Mar 12, 2026 | 3:27 PM EDT
Mar 11, 2026 | 12:25 PM EDT
Mar 6, 2026 | 5:44 PM EST
Mar 5, 2026 | 1:57 PM EST
Mar 17, 2026 | 11:38 AM EDT
Mar 15, 2025 | 10:58 AM EDT
Dec 9, 2024 | 4:46 PM EST
Aug 9, 2024 | 5:23 PM EDT
May 2, 2024 | 9:42 AM EDT
Nov 12, 2023 | 4:02 PM EST
Jan 2, 2026 | 3:26 PM EST
Dec 19, 2025 | 11:34 AM EST
Dec 18, 2025 | 1:38 PM EST
Dec 12, 2025 | 1:48 PM EST
Dec 3, 2025 | 4:59 PM EST
Aug 23, 2025 | 10:57 AM EDT
Aug 27, 2025 | 10:46 AM EDT
Jul 8, 2025 | 9:26 AM EDT
Jan 14, 2024 | 1:30 PM EST
Dec 6, 2023 | 7:12 PM EST
Dec 4, 2023 | 6:44 PM EST
Nov 25, 2023 | 2:00 PM EST
Mar 13, 2026 | 5:02 PM EDT
Mar 12, 2026 | 3:27 PM EDT
Mar 11, 2026 | 12:25 PM EDT
Mar 6, 2026 | 5:44 PM EST
Mar 5, 2026 | 1:57 PM EST
Mar 4, 2026 | 4:12 PM EST
Mar 17, 2026 | 12:27 PM EDT
Mar 12, 2026 | 2:27 PM EDT
Mar 11, 2026 | 4:10 PM EDT
Mar 6, 2026 | 5:02 PM EST
Mar 6, 2026 | 4:43 PM EST
Feb 27, 2026 | 5:43 PM EST
Mar 17, 2026 | 12:27 PM EDT
Mar 11, 2026 | 4:10 PM EDT
Feb 25, 2026 | 2:56 PM EST
Feb 23, 2026 | 3:38 PM EST
Dec 26, 2025 | 3:12 PM EST
Nov 28, 2025 | 10:19 AM EST
Mar 12, 2026 | 2:27 PM EDT
Mar 6, 2026 | 5:02 PM EST
Mar 6, 2026 | 4:43 PM EST
Feb 27, 2026 | 5:43 PM EST
Feb 19, 2026 | 5:04 PM EST
Feb 4, 2026 | 5:52 PM EST
Mar 12, 2026 | 2:27 PM EDT
Mar 6, 2026 | 4:43 PM EST
Feb 4, 2026 | 5:35 PM EST
Feb 4, 2026 | 3:12 PM EST
Jan 20, 2026 | 5:36 PM EST
Dec 26, 2025 | 1:25 PM EST
Mar 17, 2026 | 3:51 PM EDT
Mar 13, 2026 | 4:23 PM EDT
Mar 13, 2026 | 12:07 PM EDT
Mar 12, 2026 | 5:17 PM EDT
Mar 11, 2026 | 2:44 PM EDT
Mar 10, 2026 | 3:52 PM EDT
Mar 13, 2026 | 4:23 PM EDT
Feb 24, 2026 | 3:15 PM EST
Feb 4, 2026 | 2:58 PM EST
Jan 30, 2026 | 12:48 PM EST
Jan 28, 2026 | 3:31 PM EST
Jan 26, 2026 | 1:22 PM EST
Mar 10, 2026 | 3:52 PM EDT
Feb 13, 2026 | 3:08 PM EST
Feb 5, 2026 | 12:05 PM EST
Jan 30, 2026 | 1:36 PM EST
Jan 22, 2026 | 5:57 PM EST
Jan 22, 2026 | 5:16 PM EST
Mar 13, 2026 | 12:07 PM EDT
Mar 12, 2026 | 5:17 PM EDT
Mar 11, 2026 | 2:44 PM EDT
Jan 27, 2026 | 10:57 AM EST
Jan 26, 2026 | 4:23 PM EST
Jan 23, 2026 | 2:49 PM EST
Jan 29, 2026 | 2:02 PM EST
Dec 10, 2025 | 5:29 PM EST
Aug 12, 2025 | 2:55 PM EDT
Jun 20, 2025 | 2:52 PM EDT
Jun 20, 2025 | 2:11 PM EDT
Jun 20, 2025 | 11:34 AM EDT
Mar 19, 2026 | 4:01 PM EDT
Mar 18, 2026 | 12:12 PM EDT
Mar 5, 2026 | 3:40 PM EST
Mar 5, 2026 | 12:29 PM EST
Mar 3, 2026 | 4:07 PM EST
Feb 27, 2026 | 12:14 PM EST
Mar 19, 2026 | 4:01 PM EDT
Mar 18, 2026 | 12:12 PM EDT
Mar 5, 2026 | 3:40 PM EST
Mar 5, 2026 | 12:29 PM EST
Mar 3, 2026 | 4:07 PM EST
Feb 27, 2026 | 12:14 PM EST
Update Sept. 23, 2025, at 4:52 p.m. ET: Public Mobile said it fixed the RCS issues plaguing several of its customers. In a message sent by the carrier’s support team to impacted customers, it said it fixed the problem and detailed steps customers could take to restore RCS functionality.
Android steps include clearing the Messages app’s storage and cache, force-closing the app, opening it, and checking the RCS status (more detailed steps on how to do this can be found further down in the article). For iPhone users, Public says to reset the network settings, which can be found in Settings > General > Transfer or reset iPhone > Reset > Reset Network Settings. (This will clear all saved Wi-Fi networks and passwords, cellular settings, and Bluetooth pairings.)
After clearing the storage on my Pixel 10 Pro’s Messages app, RCS started working again for me. Additionally, a MobileSyrup reader confirmed to me that RCS started working on his iPhone. However, if you’re still experiencing issues, please email me at [email protected].
The original story continues below.
Customers of Telus-owned wireless carrier Public Mobile are dealing with an ongoing Rich Communication Services (RCS) issue, with no end in sight.
Several Public Mobile customers (including myself) have lost access to RCS after moving their physical SIM or eSIM to a new phone. The problem causes RCS setup to fail, preventing users from sending or receiving RCS messages, though SMS and MMS continue to work. I first encountered the issue roughly two weeks ago after moving my physical Public SIM card from a Pixel 10 to a Pixel 10 Pro so I could start testing the phone for my review.
Since encountering the issue, I’ve been chatting back and forth with Public Mobile’s support and performing lots of troubleshooting steps (both on my own and with Public’s support) to try and resolve the issue. However, nothing worked.
I initially thought it was just me since I often switch phones for work purposes; I probably screwed something up with RCS along the way. It wasn’t until Sept. 21 that I began to suspect the problem might be a broader issue when a message from a Public support agent noted that Public was “aware of this situation” and that technicians were “working as quickly as possible to resolve it for you and all the people affected.”
Moreover, MobileSyrup received notes from readers who also encountered problems, and there are several threads on Reddit and Public’s own forums detailing the ongoing issue. Tons of Public Mobile customers, including both iPhone and Android users, have encountered RCS disruptions after changing phones. Some iPhone users also noted that RCS stopped working after upgrading to iOS 26, though it’s not clear if or how these problems are connected.

On my Pixel 10 Pro, the RCS settings page in the Google Messages app showed that it was attempting to set up RCS for several hours before eventually switching to a message saying that RCS is “Not supported” by Public Mobile. This isn’t true — RCS works fine with Public Mobile, and if I pop my SIM back into the Pixel 10, RCS works fine. It seems most people impacted by the issue are seeing similar messages or errors in their respective messaging apps and settings.
On Sept. 22, I received a text message from Public Mobile’s support team explaining that the company was investigating “a known issue with RCS Chat.” The message warned that it might take “a few days or a few weeks” to resolve, and the company recommended performing some troubleshooting steps every couple of days to check if RCS has started working.
However, given that the RCS outage has already been ongoing for several weeks, hearing that it could take a few more weeks to fully resolve is less than ideal. MobileSyrup also reached out to Public Mobile owner Telus about the issue, and received the following statement:
“Some Public Mobile customers may experience issues activating RCS messaging services after transferring their physical SIM card or eSIM to a new device. We are aware of the situation and our Public Mobile team is currently investigating with our technology partners. Customers are still able to send standard SMS and picture messages with their device at this time.”
However, Telus did not answer questions about what caused the problem, how widespread it is, and when customers can expect a resolution.
If you’re encountering the RCS issue, here are some steps you can try that might help, though so far, I’ve attempted these multiple times with no fix yet. Moreover, the steps below are specifically for Android devices, as that’s what I have and what I’ve been troubleshooting.

If that doesn’t fix the problem, try the following:

Again, I’ve been trying the above every couple of days to see if things come back online, but so far, none of this has worked for me. However, with Public now aware of the problem, hopefully it won’t be too much longer before this all gets sorted out.
Thanks Scott!
MobileSyrup may earn a commission from purchases made via our links, which helps fund the journalism we provide free on our website. These links do not influence our editorial content. Support us here.
Sign-up for MobileSyrup news sent straight to your inbox
By submitting your information, you agree to receive electronic communications from MobileSyrup, containing news, updates and promotions regarding MobileSyrup’s products. You may withdraw your consent at any time.
By submitting your information, you agree to receive electronic communications from MobileSyrup, containing news, updates and promotions regarding MobileSyrup’s products. You may withdraw your consent at any time.
By submitting your information, you agree to receive electronic communications from MobileSyrup, containing news, updates and promotions regarding MobileSyrup’s products. You may withdraw your consent at any time.
© 2026 ZoomerMedia Privacy. Terms of use.

source