User level: Level 1 (4 points)ios27 after update cellular label names do not persist.
Problem: User is trying to label an additional cell line and uses the edit to make a custom label, which does persist until the user switches the cell plan off. When coming back to turn that cell plan on which does have the custom label it then asks for data or data+cellular for the plan and then default labels it to Travel and the custom cellular name that was previously saved does no persist.
Posted on Sep 26, 2026 7:44 PM
User level: Level 10 (454,138 points)Sep 27, 2026 12:17 AM in response to user-100
On my iPhone 13 running iOS 27, I have a cellular plan that is currently switched off and has a custom label, “Google Fi Ra…”. When I switch the cellular plan back on, the custom label remains intact; it is not replaced by a default label such as “Travel.”
This indicates that the behavior being described is not necessarily an iOS 27-wide issue. Since the same iOS version preserves the custom cellular-plan label on my iPhone 13, the difference could be device-specific, carrier/eSIM-specific, or related to the particular way that cellular plan is configured.
Therefore, it would be premature to conclude that iOS 27 itself is responsible for resetting the custom label. To establish that, the same cellular plan and carrier configuration would need to be tested on another device, or the behavior reproduced with different carriers/eSIMs on the affected device.
See the pic below
User level: Level 1 (8 points)Nov 4, 2026 3:58 PM in response to SravanKrA
I have two iPhone 12s, both of which have the problem and I highly suspect this is isolated to iPhones with no dual-eSIM standby capability.
Due to the declining user base of iPhone 12 or earlier, they may treat it as an isolated bug.
To recreate the bug, you need to have at least 1 eSIM, turn it off, then boot exclusively with the physical SIM.
User level: Level 10 (454,138 points)Sep 26, 2026 11:27 PM in response to user-100
user-100 wrote:
ios27 after update ...
Not every issue an individual encounters on their device can be attributed to an iOS update. 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 systemic, but rather specific to the device in question.
User level: Level 10 (454,138 points)Sep 26, 2026 11:28 PM in response to user-100
Please note that this is a public forum, so when attaching a screenshot, please avoid including any personal credentials such as IP addresses, card details, email IDs, Apple IDs, IMEI numbers, serial numbers, phone numbers, order IDs, invoices, or any identifiable location information if you are sharing a map and avoid using inappropriate phrases and abbrevations.
Originally posted at discussions.apple.com/thread/256365719