Text Message Forwarding toggle keeps turning on independently

If Text Message Forwarding is enabled on your iPhone, first check which Apple devices are receiving the forwarded messages. Messages can be forwarded to devices such as a Mac, iPad, or another iPhone that is signed in with the same Apple Account and configured for Messages.

On your iPhone, go to Settings → Apps → Messages → Text Message Forwarding and check the list of devices. You can turn forwarding off for any device you do not want to receive your SMS messages. If necessary, you can also disable the corresponding Messages/Text Message Forwarding settings directly on the other Apple devices.

However, there is an important distinction here. If by “text message forwarding” you mean that your mobile carrier is forwarding your SMS messages to another phone number, service, or device, that is a completely different mechanism. Carrier-level SMS forwarding is controlled by the network operator, not by the iPhone's Text Message Forwarding feature.

Since you have not specified where the messages are being forwarded or what device/number is receiving them, the first step is to determine whether this is Apple's Text Message Forwarding feature or carrier-level SMS forwarding.

• Forwarding to a Mac, iPad, or another Apple device: Check and disable it under Text Message Forwarding on the iPhone.
• Forwarding to another phone number or through the mobile network: Contact your carrier, because the carrier controls that service and changing iPhone settings will not resolve it.

In other words, Apple-device forwarding is an iPhone/Apple Account setting; carrier-level forwarding is a mobile-network issue. Identifying which type of forwarding is occurring is essential before troubleshooting further.

askingaquestiontoday wrote:

... until updates,

Not every issue an individual encounters on their device can be attributed to an iOS update. iOS 27 may have coincided with what you are experiencing, but that does not mean the issue was triggered by iOS 27. Coincidence in timing is not, by itself, evidence of causation.

If the update itself were the root cause, then every device running that same version of iOS would exhibit the identical problem. In such a scenario, the forums would be flooded with countless posts reporting the same malfunction, creating an unmistakable wave of complaints that no one could possibly overlook.

The absence of such widespread reports strongly indicates that the issue is not a general, system-wide problem with iOS 27, but rather something specific to the individual device, its configuration, installed apps, settings, hardware, or another interacting factor.

In short: iOS 27 may be a coincidence in timing, but there is no basis to conclude that iOS 27 itself triggered the problem simply because the issue appeared after the update.