RCS is a modern text service, similar to iMessage. It gives End to End Encryption (E2EE), typing dots, read receipts, allows sending larger photos, and group chats over mobile data or Wi-Fi. However, sometimes users fail to register with RCS. In these cases, Google Messages will show a status code. The code says why RCS off or stuck.
Basic troubleshooting
Check that the SIM is in the phone and shows signal.
Make Google Messages the default text app.
Make sure that Google Messages, Google Play services, and the Google Play Store have the necessary permissions (see the RCS on GrapheneOS article for more info).
Open Messages, then Settings, then RCS chats. Turn it off, wait 30 seconds and turn it on.
Restart the phone.
Groups
Numbers
Group
In short
0 and -1
Unknown
Google Messages doesn't recognize the state it is in
1000s
RCS is not supported
Google Messages has deemed the device ineligible for RCS registration
2000s
Connection
These codes show that Google Messages is attempting to register
3000s
Setup errors
Google Messages sets up RCS, or setup hit a problem
3100s
ACS Errors
Errors when Google Messages asks the carrier for RCS provisioning data
3200s
UPI Errors
Errors when Google Messages verifies the phone number
3300s
ICC Auth errors
Errors during ICC auth (SIM-based authentication with the carrier)
4000s
Carrier rules
A Carrier Config has disabled RCS
Unknown
Code
Enum
Why it happens
What to try
0
CODE_UNKNOWN
Google Messages has no status code for the error it is experiencing.
Update Google Messages.
-1
UNRECOGNIZED
Google Messages received an unknown status code.
Update Google Messages.
1000s: RCS is not supported
Code
Enum
Why it happens
What to try
1000
CODE_NOT_SUPPORTED_RCS_TURNED_OFF
RCS is off.
Open Messages, Settings, RCS chats, and turn it on.
1001
CODE_NOT_SUPPORTED_SIM_ABSENT
Google Messages could not find a SIM.
Make sure that Google Messages and Google Play Services have the correct permissions, and that the SIM is enabled
1002
CODE_NOT_SUPPORTED_SIM_INELIGIBLE
The carrier's entitlement service returned RCS as ineligible for this SIM.
This should never occur on Cape.
1003
CODE_NOT_SUPPORTED_DEVICE_INELIGIBLE
The phone cannot use RCS. Google Messages has, for whatever reason, deemed the device ineligible for RCS registration.
Ensure you are on the latest version of the OS, and that your phone has not hit its EoL date.
1004
CODE_NOT_SUPPORTED_NOT_DEFAULT_SMS_APP
Google Messages is not the default text app.
Set Google Messages as the default SMS app.
1005
CODE_NOT_SUPPORTED_REGION_INELIGIBLE
RCS is off for this region.
The user is in a region where Google has disabled RCS.
1006
CODE_NOT_SUPPORTED_DISABLED_IT_ADMIN
MDM policy disabled RCS.
Ask the IT admin to allow RCS. Check for a work profile on the phone.
1007
CODE_NOT_SUPPORTED_DISABLED_PROVISIONING_RULE
The carrier configs disable RCS.
This should never occur on Cape.
1008
CODE_NOT_SUPPORTED_NO_PERMISSIONS
Google Messages does not have a permission it needs to register.
Ensure Google Messages, Google Play Services, and Google Play Store have access to Phone, SMS, and Internet. If on GrapheneOS, enable ICC auth access for Google Play Services.
1009
CODE_NOT_SUPPORTED_SECONDARY_USER
Google Messages disables RCS registration on secondary users.
Switch to the Owner profile.
2000s: Connection
Code
Enum
Why it happens
What to try
2000
CODE_CONNECTED
RCS works. This is the normal state.
RCS is working, there's nothing to fix.
2001
CODE_CONNECTING
Google Messages is registering.
Wait a few minutes.
2002
CODE_CONNECTION_UNAVAILABLE
Google Messages cannot access the internet.
Check mobile data or Wi-Fi. Toggle airplane mode. Turn RCS chats off and on. Restart. If on GrapheneOS, ensure Google Messages has the internet permission allowed.
3000s: Setup errors
Code
Enum
Why it happens
What to try
3000
CODE_PROVISIONING_IN_PROGRESS
Google Messages is provisioning RCS.
Wait up to 10 minutes.
3001
CODE_PROVISIONING_FAILED
Setup failed with no more detail.
Do basic troubleshooting.
3002
CODE_MANUAL_MSISDN_DAILY_LIMIT_REACHED
The phone number (MSISDN) tried to register too many times today.
Wait 24 hours for the ratelimit to expire.
3003
CODE_FORCE_MANUAL_MSISDN_LIMIT_REACHED
The server ratelimited this phone number (MSISDN).
Wait 24 hours for the ratelimit to expire.
3004
CODE_SIM_ROAMING
RCS setup stopped because the SIM is roaming internationally.
Currently, RCS will fail to register when roaming internationally on Cape (due to the IMSI's PLMN not being 314/560 whilst roaming).
3005
CODE_CELLULAR_CONNECTIVITY_UNAVAILABLE
Setup needs mobile data for header enrichment.
This should never occur on Cape.
3006
CODE_FI_NOT_ACTIVATED
Google Fi is not active on this line.
This is a Google Fi specific error code and should never occur on Cape.
3007
CODE_RCS_CONSENT_NEEDED
Google Messages needs the user to consent before it turns on RCS.
Open Google Messages and enable RCS.
3008
CODE_EXPLICIT_TOS_CONSENT_NEEDED
The user must accept the carrier terms of service.
This should never occur on Cape.
3009
CODE_AMBER_SYNC_IN_PROGRESS
A sync step is running. This code also shows when Google services turn RCS off for the device. This should only occur if you are logged in to a Google Account and have message sync enabled.
Wait a few minutes.
3100s: ACS Errors
Code
Enum
Why it happens
What to try
3100
CODE_ACS_RESPONSE_FAILED
The carrier server sent a failed reply.
Retry later. This error usually means there is a network issue on our end.
3101
CODE_ACS_OTP_THROTTLED
The user asked for too many one-time codes.
Wait 24 hours for the ratelimit to expire.
3102
CODE_ACS_OTP_TIMEOUT
The one-time code did not arrive in time.
Check that your phone is connected to the mobile network and that the SIM can receive SMS. Turn off SMS filters. Retry.
3103
CODE_ACS_NETWORK_ERROR
A network problem stopped the request.
Check mobile data and Wi-Fi. Toggle airplane mode. Retry.
3200s: UPI errors
Code
Enum
Why it happens
What to try
3200
CODE_UPI_RESPONSE_FAILED
The server returned a server-side failure.
Try again later. This error usually means there is a network issue on our end.
3201
CODE_UPI_OTP_THROTTLED
The user asked for too many one-time codes.
Wait 24 hours for the ratelimit to expire.
3202
CODE_UPI_RPC_THROTTLED
The server ratelimited you.
Wait 24 hours for the ratelimit to expire.
3203
CODE_UPI_SIM_NOT_IN_SERVICE
The carrier says the SIM is not in service.
Check that the line is active. Re-download the eSIM.
3204
CODE_UPI_NETWORK_ERROR
A network problem stopped registration.
Check mobile data and Wi-Fi. Toggle airplane mode. Retry.
3205
CODE_UPI_CARRIER_INELIGIBLE
The carrier does not allow RCS for this line.
This should never occur on Cape.
3300s: ICC Auth errors
Code
Enum
Why it happens
What to try
3300
CODE_TS43_AUTH_FAILED
Google Messages could not perform ICC authentication.
If on Graphene, ensure Google Play Services has access to ICC auth.
3301
CODE_TS43_AUTH_THROTTLED
ICC auth hit a rate limit.
Wait 24 hours for the ratelimit to expire.
3302
CODE_TS43_AUTH_CONTENT_ERROR
ICC auth got an invalid response.
Try again later.
3303
CODE_TS43_AUTH_NETWORK_ERROR
A network problem interrupted ICC auth.
Check mobile data and Wi-Fi. Toggle airplane mode. Try again later.
3304
CODE_TS43_GET_TEMP_TOKEN_FAILED
Getting a temporary token failed.
Try again later. Do basic troubleshooting.
3305
CODE_TS43_GET_TEMP_TOKEN_CONTENT_ERROR
The reply had invalid content.
Try again later.
3306
CODE_TS43_GET_TEMP_TOKEN_INELIGIBLE
The carrier refused to perform ICC authentication.
This should never occur on Cape.
3307
CODE_TS43_GET_TEMP_TOKEN_NETWORK_ERROR
A network problem interrupted ICC auth.
Check mobile data and Wi-Fi. Toggle airplane mode. Try again later.
3308
CODE_TS43_REQUEST_TEMP_TOKEN_FAILED
Requesting a temporary token failed.
Try again later. Do basic troubleshooting.
3309
CODE_TS43_REQUEST_TEMP_TOKEN_THROTTLED
The user asked for too many tokens.
Wait 24 hours for the ratelimit to expire.
3310
CODE_TS43_REQUEST_TEMP_TOKEN_CONTENT_ERROR
The reply had invalid content.
Try again later.
3311
CODE_TS43_REQUEST_TEMP_TOKEN_NETWORK_ERROR
A network problem stopped the request.
Check mobile data and Wi-Fi. Toggle airplane mode. Try again later.
4000s: Carrier config errors
Code
Enum
Why it happens
What to try
4000
CODE_CONFIG_INVALID
The Carrier Configs are not valid.
Try again later. Clear Google Messages' app storage.
4001
CODE_CONFIG_INVALID_POS_VALIDITY
Carrier Configs have a bad "valid for" time.
Try again later. Clear Google Messages' app storage.
4002
CODE_CONFIG_CARRIER_INELIGIBLE
Carrier Configs disable RCS.
This should never occur on Cape.
4003
CODE_CONFIG_REGION_INELIGIBLE
Carrier Configs disable RCS in this region.
Currently, RCS will fail to register when roaming internationally on Cape (due to the IMSI's PLMN not being 314/560 whilst roaming).
4004
CODE_CONFIG_APP_VERSION_INELIGIBLE
Carrier Configs require a newer version of Google Messages.
Update Google Messages.
4005
CODE_CONFIG_VENDOR_INELIGIBLE
Carrier Configs do not allow this type of phone to register with RCS.
This should never occur on Cape.
4006
CODE_CONFIG_SECURITY_INELIGIBLE
A security check blocked RCS.
Open Google Messages and check for any prompts. Follow the troubleshooting steps for code 3300.
4007
CODE_CONFIG_FI_SYNC_ENABLED
Google Fi sync is on for this line.
This is a Google Fi specific error code and should never occur on Cape.