DEV Community: Marc Gonzalez

eSIM Transfer: Protocol Constraints and Device-Specific Implementations

Marc Gonzalez — Mon, 31 Aug 2026 13:54:47 +0000

What eSIM Transfer Actually Does at the Protocol Level

eSIM transfer is not a true profile migration. When you "transfer" an eSIM, the original profile is deleted and a new profile is provisioned to the target device's Embedded Universal Integrated Circuit Card Identifier (EID) via the carrier's Subscription Manager Data Preparation (SM-DP+) server. Apple's eSIM Quick Transfer automates this for same-ecosystem moves, but Android has no equivalent cross-device API—you must use your carrier's app or request a new QR code.

According to Apple's support documentation, an eSIM is a digital SIM built into your device. Each eSIM has a unique EID that cryptographically binds profiles to specific hardware. A profile provisioned to EID A cannot execute on EID B. What users perceive as "transfer" is actually:

Authentication of the transfer request with the carrier
Deletion of the profile from the source device's eUICC
Generation of a new profile bound to the target device's EID
Download and installation via the Remote SIM Provisioning (RSP) protocol

This architecture explains why you cannot simply copy an eSIM file between devices. The profile contains carrier credentials encrypted for a specific EID, and the SM-DP+ server enforces this binding.

Apple's eSIM Quick Transfer: Carrier-Mediated Profile Swap

Apple's eSIM Quick Transfer automates the deletion-and-reprovisioning sequence for iPhone-to-iPhone transfers. The mechanism requires:

Both devices signed into the same Apple Account
The previous iPhone unlocked with its device passcode
Both devices nearby with Bluetooth enabled
Carrier support for eSIM Quick Transfer

During setup of a new iPhone, the system detects nearby devices with transferable profiles. When you select a line to transfer, the new iPhone communicates the transfer request to Apple's servers, which coordinate with the carrier's SM-DP+ server. The carrier validates the request, generates a new profile bound to the new device's EID, and pushes it via the Local Profile Assistant (LPA) on the new iPhone.

According to Apple's support documentation, "the cellular plan on your new iPhone deactivates your previous SIM when it activates." This is not instantaneous profile migration—the old profile is deleted as part of the activation sequence.

Some carriers require an additional step. If a banner appears stating "Finish Setting Up Your Carrier's Cellular Plan," the transfer is incomplete. Tapping the banner redirects you to the carrier's webpage to authorize the profile generation. This indicates the carrier has not fully automated their SM-DP+ integration with Apple's transfer API.

You can also convert a physical SIM to an eSIM on supported carriers using the same Quick Transfer interface, selecting "Convert to eSIM" instead of a device-to-device transfer.

Android eSIM Handling: No Cross-Device Transfer API

Android implements the GSMA RSP specification for profile download and management but provides no native API for device-to-device transfer. On Pixel devices, Pixel 3a and later support one physical SIM plus one eSIM, with Dual SIM Dual Standby (DSDS) allowing both to remain active simultaneously.

To move an eSIM to a new Android device, you must:

Install your carrier's official app on the new device
Authenticate with your account credentials
Navigate to device management or line activation
Provide the new device's IMEI or EID (found in Settings → About phone → SIM status)
Authorize the transfer, typically via SMS to the old device

This workflow is carrier-specific. T-Mobile uses the T-Life app, Verizon uses My Verizon, AT&T uses myAT&T. Each implements its own UI for triggering SM-DP+ reprovisioning. The carrier's backend deletes the old profile and generates a new QR code or pushes a profile directly to the new device's EID.

Google's DSDS implementation allows two profiles to remain active simultaneously, but this is a radio-level feature, not a transfer mechanism. You still provision each profile independently.

Cross-Platform Transfer: Why Android-to-iPhone Works Differently

Apple's support documentation lists "Transfer an eSIM from an Android or other non-Apple device" as a distinct method from iPhone-to-iPhone Quick Transfer. Cross-platform transfer cannot use Apple's automated flow because Android devices do not participate in Apple's device-proximity protocol.

The process requires full carrier involvement:

On the iPhone, navigate to Settings → Cellular → Add eSIM
Select your carrier from the list (if available) or choose "Use QR Code"
The carrier's activation flow will require authentication
The carrier's SM-DP+ server provisions a new profile to the iPhone's EID
The Android device's profile is deactivated by the carrier backend

This is functionally identical to activating a new line—the carrier treats the iPhone as a new device requesting service. The Android device does not participate in the transfer beyond potentially receiving an authorization SMS.

Some carriers provide a web portal where you can initiate the transfer by entering both devices' EIDs. This triggers the same backend sequence: delete the old profile, generate a new one, push it to the target EID.

GSMA RSP Architecture: What the Spec Defines and What It Doesn't

The GSMA's SGP.21 and SGP.22 specifications define the architecture and technical implementation of Remote SIM Provisioning. Multiple specification versions remain active simultaneously for backward compatibility.

These specifications standardize:

The SM-DP+ server's role in profile generation and encryption
The LPA's role in profile download and installation on the eUICC
Profile lifecycle states (enabled, disabled, deleted)
The ES8+ interface between SM-DP+ and eUICC
Profile metadata and notification mechanisms

What the specifications do not standardize:

Device-to-device transfer protocols
User interfaces for transfer initiation
Cross-platform transfer workflows
Automatic profile migration on device replacement

The GSMA RSP architecture assumes that profile provisioning is always a server-driven operation. The SM-DP+ server is the source of truth. Device-to-device transfer is not a peer-to-peer operation—it is a coordinated delete-and-reprovision orchestrated by the carrier's backend.

This explains why Apple's Quick Transfer and carrier-specific Android apps implement transfer so differently. The GSMA spec provides the primitives (profile deletion, profile download, EID binding) but leaves the user-facing workflow to platform vendors and carriers.

Dual-SIM Configurations and Profile Limits

Apple's implementation allows an iPhone XS, iPhone XR, or later to store eight or more eSIMs, but only one can be active at a time unless the device supports dual-SIM operation (one physical SIM plus one eSIM, or two eSIMs on iPhone 13 and later in regions where physical SIM trays are absent).

On Android, Pixel 4a (5G) and later models with dual-SIM support can connect to 5G networks, but 5G availability depends on carrier provisioning and network compatibility. Some carriers restrict 5G to the primary SIM slot.

Storage limits are eUICC hardware constraints. When you attempt to download a new profile to a full eUICC, the LPA will prompt you to delete an existing profile. Deleted profiles can be re-downloaded from the carrier's SM-DP+ server if the carrier retains the profile data, but this is not guaranteed. Some carriers generate single-use profiles that cannot be re-downloaded after deletion.

Troubleshooting Transfer Failures: Implementation Gaps

Transfer failures typically occur at the carrier integration layer, not the device layer. Common failure modes:

"Finish Setting Up Your Carrier's Cellular Plan" banner: The carrier's SM-DP+ server generated a profile but requires additional authentication. This banner indicates a carrier webpage redirect is required. The carrier has not fully automated their activation flow with Apple's API. You must complete the web-based activation to finalize the profile installation.

"Transfer Failed" during Quick Transfer: The carrier's backend rejected the transfer request. Possible causes:

The source device is not unlocked or the passcode was not entered
The carrier account has restrictions (unpaid balance, fraud hold)
The carrier does not support eSIM Quick Transfer for your plan type
The target device's EID is not in the carrier's device whitelist

Transfer requires the previous iPhone to be unlocked with the device passcode because the LPA must authenticate the deletion request. If the device is locked, it cannot confirm profile removal to the carrier's SM-DP+ server.

QR code scan fails on Android: The QR code encodes an SM-DP+ server address and activation code. Scan failures occur when:

The QR code has expired
The device's LPA cannot reach the SM-DP+ server (network issue)
The activation code has already been used

Generate a new QR code from the carrier's portal or app. Activation codes are single-use tokens.

Profile downloads but does not activate: The profile installed successfully but the carrier's Home Location Register (HLR) has not updated. This is a carrier backend issue. Wait several minutes for HLR propagation, then toggle Airplane Mode to force a network re-registration. If the issue persists, contact the carrier—the profile is installed but not authorized on the network.

What Developers Should Know

If you are building an app that interacts with eSIM provisioning:

On iOS, use the CTCellularPlanProvisioning API to trigger profile downloads. You cannot implement device-to-device transfer—that requires carrier integration with Apple's backend. You can, however, provide a QR code or activation code that the user scans via Settings → Cellular → Add eSIM.

On Android, use the EuiccManager API to list installed profiles, download new profiles, and switch between profiles. The downloadSubscription method accepts an activation code from your carrier's SM-DP+ server. You cannot access another device's profiles or implement peer-to-peer transfer.

For carrier integrations, implement the GSMA SGP.22 ES2+ interface between your SM-DP+ server and the device's LPA. Support both QR code activation (for manual setup) and push provisioning (for automated flows). If you want to support Apple's Quick Transfer, work with Apple's carrier engineering team to integrate your SM-DP+ server with their transfer API.

For cross-platform apps, assume that eSIM transfer requires user interaction with your carrier portal or app. Provide clear instructions for obtaining a new QR code or activation code. Do not promise seamless transfer—the GSMA architecture does not support it, and platform implementations vary.

When a user reports that they "cannot transfer" an eSIM, the issue is almost always carrier policy or backend configuration, not device capability. The device can download and install any profile the SM-DP+ server provides. If the carrier's backend does not support reprovisioning to a new EID, no amount of device-side troubleshooting will resolve it.

Dual-SIM iPhone: eSIM provisioning, DSDS behaviour and QR activation

Marc Gonzalez — Mon, 31 Aug 2026 06:08:10 +0000

Does the iPhone support dual-SIM?

Yes. iPhone XS, XS Max, XR and all later models support dual-SIM operation using one physical nano-SIM and one eSIM, or two eSIMs simultaneously. US models from iPhone 14 onward removed the physical SIM tray entirely and rely exclusively on dual eSIM. Regional exceptions apply: in China mainland, eSIM support is limited; Hong Kong and Macao models feature dual nano-SIM slots instead.

You activate the second line through one of three methods: scanning a QR code provided by your carrier, automatic carrier activation via an entitlement server, or eSIM Quick Transfer from another iPhone. Both lines stay registered with their networks, so either number can receive calls and messages without manual switching — but only one line can carry traffic at a time. That is Dual SIM Dual Standby (DSDS), which is what iPhone implements; it is not Dual SIM Dual Active (DSDA), where both radios operate at once.

eSIM provisioning methods

QR code and SM-DP+ activation

The QR code your carrier provides encodes an SM-DP+ server address and an activation code. When you scan it in Settings → Cellular → Add eSIM, iOS contacts the SM-DP+ server, authenticates using the activation code, and downloads the eSIM profile to the device's embedded Universal Integrated Circuit Card (eUICC). This is the LPA (Local Profile Assistant) flow defined in GSMA SGP.22.

The profile contains IMSI, Ki, carrier APN settings, and network authentication credentials. Once installed, the profile appears as a selectable line in Settings → Cellular. You need a Wi-Fi or hotspot connection for activation in most regions; some eSIM-only models activate without Wi-Fi in specific markets.

If the QR code has already been claimed by another device, the SM-DP+ server returns an error and iOS displays "This code is no longer valid." The activation code is single-use by design; you must request a new QR code from your carrier.

Carrier activation

Carriers that support eSIM Carrier Activation provision profiles directly via an entitlement server without requiring a QR code. When you insert a physical SIM or connect to the carrier's network, iOS queries the carrier's entitlement API. If an eSIM profile is available for your account, iOS prompts you to install it.

This flow is common for users upgrading within the same carrier or activating a new line during iPhone setup. The carrier's backend associates your IMEI with an eSIM profile and pushes it to the device when you authenticate.

eSIM Quick Transfer

eSIM Quick Transfer requires both devices to run iOS 18 or later, the same Apple Account signed in, and Bluetooth enabled. During setup of a new iPhone, iOS detects nearby devices and offers to transfer the eSIM profile directly over a local encrypted channel.

The transfer flow:

New iPhone broadcasts a Bluetooth LE advertisement.
Old iPhone receives the pairing request and displays a confirmation prompt.
User taps Transfer on the old device.
iOS establishes a peer-to-peer Wi-Fi connection (not infrastructure Wi-Fi).
The eSIM profile is re-provisioned to the new device via the carrier's entitlement server; the old device's profile is deactivated.

This is not a literal profile copy—the carrier's SM-DP+ server issues a new profile to the new device and revokes the old one. If the transfer fails mid-flight, the profile remains active on the original device and you can retry.

You can also convert a physical SIM to an eSIM using Quick Transfer if your carrier supports it. The flow is identical; iOS contacts the carrier's API to provision an eSIM profile and deactivates the physical SIM.

Dual standby behaviour

iOS implements Dual SIM Dual Standby (DSDS), not Dual SIM Dual Active. Both lines register with their respective networks and either can receive calls and SMS while idle, but the device has a single active radio chain: the moment one line is in a call, the other cannot carry traffic. When a call arrives on Line 1 while you are on a call on Line 2, iOS displays a call-waiting notification. You can hold the active call and switch, or decline the incoming call.

Data line selection

Only one line can use cellular data at a time. You designate a default data line in Settings → Cellular → Cellular Data. If the default line loses coverage, iOS can switch data to the secondary line automatically if you enable "Allow Cellular Data Switching." This setting appears only when both lines are active.

When Allow Cellular Data Switching is on and the primary data line has no service, iOS uses the secondary line for data and displays "Using [Line Name] for Cellular Data" in Control Centre. Voice calls on the primary line still route over that line's network when coverage returns.

Call routing

Outgoing calls use the line you select in the Phone app's keypad. Before dialling, tap the current line label at the top of the screen to switch. iOS remembers which line you last used to contact each number and defaults to that line for subsequent calls to the same contact.

iMessage and FaceTime can be enabled on both lines simultaneously. Messages sent to your phone number route to the corresponding line; messages sent to your Apple Account email address appear on both. You can choose which line to use for new conversations in Settings → Messages → Send & Receive and Settings → FaceTime.

The eight-profile limit

The eUICC can store eight or more eSIM profiles, but only two can be active simultaneously. This is a hardware constraint of the eUICC's non-volatile memory.

When you attempt to install a ninth profile, iOS prompts you to delete an existing one. Deleting a profile removes it from the device entirely; you must re-provision it from the carrier (via QR code or entitlement server) to use it again. Some carriers allow you to download the same profile multiple times; others issue a new activation code for each installation.

To delete an eSIM profile:

Open Settings → Cellular.
Tap the line you want to remove.
Tap Delete eSIM.
Confirm the deletion.

The profile is erased from the eUICC immediately. If the line is active, it deregisters from the network within seconds.

Troubleshooting activation failures

SM-DP+ server unreachable

If iOS displays "Unable to Complete Cellular Plan Change" after scanning a QR code, the SM-DP+ server is unreachable or returned an error. Common causes:

No internet connection: Activation requires Wi-Fi or an active cellular data connection on the primary line. Connect to Wi-Fi and retry.
Incorrect QR code: The QR code may be damaged or incorrectly printed. Request a new code from your carrier.
Server-side error: The carrier's SM-DP+ server may be temporarily unavailable. Wait and retry.

Check the activation code format. A valid LPA QR code begins with LPA:1$ followed by the SM-DP+ address and activation code, for example:

LPA:1$sm-dp.example.com$ACTIVATION-CODE-STRING

If the QR code does not match this format, it is not a valid eSIM activation code.

Profile already claimed

If the activation code has been used on another device, the SM-DP+ server refuses the request and iOS displays "This code is no longer valid." Activation codes are single-use. Contact your carrier to request a new QR code or use their self-service portal to generate one.

Carrier compatibility

Your carrier must support eSIM for the activation to succeed. Apple maintains a list of compatible carriers at apple.com/uk/esim, but the list is not exhaustive. If your carrier is not listed, contact them directly to confirm eSIM availability for your plan.

Some carriers restrict eSIM to specific plan types (e.g., postpaid only) or require account verification before issuing an activation code. Prepaid eSIM availability varies by carrier and region.

APN configuration missing

After successful activation, if cellular data does not work, the APN settings may be missing or incorrect. iOS usually downloads APN settings automatically from the carrier's provisioning server, but manual configuration is sometimes required.

To check APN settings:

Open Settings → Cellular.
Tap the eSIM line.
Tap Cellular Data Network.

If the APN fields are blank, contact your carrier for the correct APN, username, and password. Enter them manually and restart the device.

Device lock status

Carrier-locked iPhones may refuse to activate eSIM profiles from other carriers. Check lock status in Settings → General → About → Carrier Lock. If the device is locked, contact the original carrier to request an unlock. Once unlocked, restart the iPhone and retry activation.

Managing two lines in practice

Choosing a provisioning method

Use eSIM Quick Transfer when moving to a new iPhone and your carrier supports it. This is the fastest method and requires no interaction with the carrier's website or support team.

Use QR code activation when adding a new line from a different carrier, activating a travel eSIM, or when Quick Transfer is unavailable. Request the QR code from your carrier's self-service portal or customer support.

Use carrier activation when your carrier provisions eSIM automatically during account setup or device purchase. This method is common for new lines purchased directly from the carrier.

Labelling lines

iOS prompts you to label each line during activation (e.g., "Personal," "Work," "Travel"). Labels appear throughout the system—in the Phone app, Messages, and Control Centre—making it clear which line you are using. You can change labels at any time in Settings → Cellular → [Line Name] → Cellular Plan Label.

Setting a default line

Designate a default line for cellular data, voice calls, and iMessage in Settings → Cellular. The default data line is used unless you manually switch or enable Allow Cellular Data Switching. The default voice line is used for outgoing calls to contacts not already associated with a specific line.

For contacts you call regularly on a specific line, iOS remembers your choice and uses that line automatically. You can override this per-contact in the Contacts app by editing the contact and setting a preferred line under "Cellular."

International travel

When travelling, you can add a local eSIM without removing your primary line. The local eSIM becomes the default data line, while your primary line remains active for incoming calls and SMS. This avoids roaming charges on your primary line while maintaining reachability.

Disable data roaming on your primary line in Settings → Cellular → [Primary Line] → Data Roaming to prevent accidental data usage. Enable it only on the local eSIM line.

What to do next

Set up dual-SIM by choosing the provisioning method your carrier supports: Quick Transfer for same-carrier upgrades, QR code for new carriers or travel eSIMs, or carrier activation for automatic provisioning. Label both lines clearly in Settings → Cellular so you can distinguish them in the Phone app and Messages. Set a default data line and enable Allow Cellular Data Switching if you need automatic failover when the primary line loses coverage. For international travel, add a local eSIM as the data line and disable roaming on your primary line to avoid charges while remaining reachable on your home number.

eSIM Activation: QR, LPA, and SM-DP+ Provisioning for Developers

Marc Gonzalez — Sun, 30 Aug 2026 19:47:45 +0000

What eSIM activation does at the protocol level

eSIM activation downloads a cryptographic profile from a carrier's SM-DP+ (Subscription Manager Data Preparation) server to your device's embedded Universal Integrated Circuit Card (eUICC). You scan a QR code, use carrier activation, or manually enter the SM-DP+ address and activation code. The Local Profile Assistant (LPA) on your phone parses the activation code, contacts the SM-DP+ server over HTTPS, authenticates the transaction, and downloads the encrypted profile to the eUICC. Once installed, the profile behaves like a physical SIM: it authenticates you to the network and stores your subscriber identity.

The underlying architecture is defined in GSMA SGP.22, the Remote SIM Provisioning (RSP) technical specification for consumer devices. The eUICC is a secure element soldered to your device's board. The profile contains your IMSI (International Mobile Subscriber Identity), authentication keys (Ki), and network access credentials. After installation, the eUICC presents these credentials to the mobile network during attach procedures, exactly as a physical SIM would. The difference is that you can install, switch, and delete profiles without physically handling hardware.

Activation methods: QR, carrier activation, and manual SM-DP+

Three standard methods exist for delivering the SM-DP+ address and activation code to your device:

QR code: The carrier generates a QR code encoding the SM-DP+ server address, activation code (or matching ID), and optionally a confirmation code. You scan this with your device camera during setup. Apple supports QR code activation on iPhone XS and later; Google supports it on Pixel 3a and later. The LPA parses the QR payload and initiates the profile download.

eSIM Carrier Activation: If your carrier supports it, the device can retrieve activation credentials directly from the carrier's backend without user input. On iOS, this appears as a prompt during setup or in Settings > Cellular > Add eSIM. The carrier's servers communicate with Apple's or Google's activation infrastructure to push the profile metadata to your device. Apple documents this as "eSIM Carrier Activation."

Manual SM-DP+ entry: You type the SM-DP+ address (a domain name like sm-v4-003-a-gtm.pr.go-esim.com) and activation code into Settings. This method is used when QR codes are impractical—for example, when you receive credentials via email or SMS. The format is typically:

SM-DP+ Address: sm-v4-003-a-gtm.pr.go-esim.com
Activation Code: LPA:1$sm-v4-003-a-gtm.pr.go-esim.com$ABC123XYZ

All three methods deliver the same information to the LPA. The choice depends on carrier infrastructure and user context.

Self-service activation: requirements and prerequisites

You can activate an eSIM yourself if your device is unlocked, supports eSIM, and you have the activation credentials.

Device requirements: Apple requires iPhone XS, iPhone XS Max, iPhone XR, or later. Google requires Pixel 3a or later. Both platforms require the device to be carrier-unlocked; a locked device will reject profiles from other carriers even if the eUICC hardware is capable.

Network requirements: You need Wi-Fi or, in some regions, an active cellular connection. Apple notes that "in some countries and regions, iPhone models that are eSIM only can activate without a Wi-Fi network," but this is carrier-dependent. The LPA must reach the SM-DP+ server over HTTPS, so network access is non-negotiable.

Credentials: You need the QR code, SM-DP+ address and activation code, or carrier app access. These are single-use in most implementations; once a profile is downloaded to a specific eUICC (identified by its EID hardware identifier), the activation code becomes invalid. If you factory-reset your device or switch devices, you must request new credentials from the carrier.

No carrier intervention is required during the actual download. The LPA and SM-DP+ handle mutual authentication and profile encryption automatically.

Dual-SIM behaviour: managing multiple profiles on iOS and Android

Modern devices can store multiple eSIM profiles and, in many cases, use two simultaneously.

iOS: Apple states that iPhones can store "eight or more eSIMs" but activate only one at a time alongside a physical SIM, or two eSIMs on devices without a physical SIM tray. You switch the active profile in Settings > Cellular by tapping the plan name and selecting "Turn On This Line." Deactivating a profile does not delete it; the profile remains in storage and can be reactivated without contacting the carrier.

Android: Google documents Dual SIM Dual Standby (DSDS) on Pixel 3a and later, allowing one physical SIM and one eSIM to be active concurrently. Pixel models that support it can run two active eSIM profiles simultaneously if the carrier permits. Some recent Pixel models support only eSIM; no physical SIM slot is present.

When two profiles are active, you choose which handles voice calls, SMS, and mobile data. Both remain registered with their respective networks, so you can receive calls on either number. Data switching is manual on iOS; on Android, you select the preferred data SIM in Settings > Network & internet > SIMs.

DSDS means both SIMs are in standby mode. If you are on a call on SIM A, SIM B may drop to 3G or become unreachable, depending on the device's radio architecture. This is a hardware limitation, not a software one.

Turning an eSIM back on (iOS)

If you deactivated an eSIM profile and need to re-enable it:

Open Settings.
Tap Cellular.
Tap the deactivated plan name. It will show "Turn On This Line" or similar.
Tap the toggle or button to activate.
Wait 10–30 seconds for the profile to register with the network.

The profile does not need to be re-downloaded. Deactivation is a state change, not a deletion. The eUICC retains the profile's cryptographic material, and reactivation is instantaneous once the network acknowledges the registration request.

If the plan does not appear in the list, it was deleted, not deactivated. You must obtain new activation credentials from the carrier and download the profile again.

Switching between physical SIM and eSIM on iPhone

To change which line handles calls, messages, or data:

Open Settings > Cellular.
Tap Cellular Data to choose the data line, or tap Default Voice Line to choose the voice/SMS line.
Select the desired SIM or eSIM.

Apple allows you to set "Allow Cellular Data Switching," which lets the device use the non-default line for data if the primary line has no signal. This is useful when roaming or in areas with asymmetric coverage.

For per-contact preferences, edit a contact and set "Preferred Line" to route calls to that contact via a specific SIM. This overrides the default voice line setting.

Troubleshooting activation failures

Common failure modes and their causes:

"Unable to Complete Cellular Plan Change": The device is carrier-locked. Even if the eUICC hardware is present, a locked device will reject profiles from carriers other than the locking carrier. Solution: contact the original carrier to unlock the device.

"SM-DP+ Address Not Reachable": The device cannot reach the SM-DP+ server. Verify Wi-Fi connectivity. Check that the SM-DP+ address is typed correctly (no spaces, correct domain). Some corporate or public Wi-Fi networks block non-HTTP/HTTPS ports or use captive portals that interfere with LPA communication. Switch to a different network.

"Activation Code Invalid": The code has already been used, or the profile was downloaded to a different device. SGP.22 allows an activation code to be bound to a specific EID, but does not require it; whether a given code is EID-bound is an operator deployment choice, not a property of the architecture. If you factory-reset your device, the EID remains the same, but the carrier's backend may have already marked the code as consumed. Request a new QR code or activation code from the carrier.

"Profile Installation Failed": The eUICC is full. iOS supports eight or more profiles, but some older devices or carrier-customised firmware may have lower limits. Delete unused profiles in Settings > Cellular > [plan name] > Remove Cellular Plan.

"Cellular Plan Not Activated" after installation: The profile downloaded successfully but failed network registration. This usually means the carrier's HLR (Home Location Register) has not yet provisioned your IMSI, or the profile's activation window has expired. Wait 10 minutes and toggle Airplane Mode. If the issue persists, contact the carrier; the problem is on their backend, not your device.

Manual network selection issues: After installing an eSIM, the device may not automatically select the correct network, especially in countries with multiple operators. Go to Settings > Cellular > [plan name] > Network Selection, disable Automatic, and manually select the carrier listed in your eSIM documentation.

What to do next

Verify your device model and iOS/Android version meet the minimum requirements (iPhone XS or later, Pixel 3a or later). Confirm the device is carrier-unlocked if you plan to use a profile from a different carrier. Obtain activation credentials—QR code, SM-DP+ address and code, or carrier app access—from your carrier or eSIM provider.

Follow the platform-specific activation flow: scan the QR code during setup or in Settings > Cellular > Add eSIM (iOS) or Settings > Network & internet > SIMs > Add eSIM (Android). If activation fails, check Wi-Fi connectivity first, then verify the activation code has not been used on another device.

For dual-SIM configurations, decide in advance which line will handle data and which will handle voice. You can change this later, but setting it correctly during activation avoids confusion when the device registers with both networks.

If you are integrating eSIM provisioning into an application, consult the GSMA SGP.22 specification for the full LPA command set and error codes. The consumer-facing flows documented here are simplified abstractions over a more complex protocol.

EPIC!

Marc Gonzalez — Tue, 07 Jul 2026 18:32:51 +0000

Marc Gonzalez

Jul 7

How eSIM Technology Actually Works: A Digital Nomad's Guide to Staying Online Abroad

#travel #global #telecom

3 min read

How eSIM Technology Actually Works: A Digital Nomad's Guide to Staying Online Abroad

Marc Gonzalez — Tue, 07 Jul 2026 18:32:07 +0000

If you've ever landed in a new country, switched off airplane mode, and watched your phone hunt for signal while roaming charges quietly stacked up — this one's for you.

Over the last few years working remotely from a dozen different countries, the single biggest quality-of-life upgrade to my setup wasn't a laptop or a VPN. It was ditching physical SIM cards and roaming for eSIM. Here's how the tech actually works under the hood, and why it's a no-brainer for anyone who works while they travel.

What is an eSIM, technically?

An eSIM ("embedded SIM") isn't a smaller SIM card — it's a small reprogrammable chip soldered directly into your phone, called an eUICC (embedded Universal Integrated Circuit Card).

A traditional SIM stores exactly one carrier profile, burned in at the factory. An eUICC can store multiple carrier profiles and download new ones over the air. This is defined by the GSMA's Remote SIM Provisioning (RSP) standard.

In plain terms: instead of physically swapping a piece of plastic, you download a carrier "profile" onto a chip that's already inside your phone.

What actually happens when you scan that QR code

When you buy a travel eSIM you get a QR code. That code isn't magic — it encodes a short activation string that looks roughly like this:

LPA:1$smdp.example.com$MATCHING-ID

Breaking it down:

LPA = Local Profile Assistant, the software on your phone that manages eSIM profiles
smdp.example.com = the address of the SM-DP+ server (Subscription Manager Data Preparation) that holds your carrier profile
MATCHING-ID = a one-time token telling the server which profile to hand you

Your phone contacts the SM-DP+ server, authenticates, downloads the profile onto the eUICC, and installs it. The whole handshake takes a few seconds. No store visit, no plastic, no waiting in line.

eSIM vs Roaming vs Local SIM

	Roaming	Local SIM	Travel eSIM
Setup	Nothing	Buy in-country, swap card	Scan a QR before you fly
Cost	Very high	Cheap	Cheap
Keep your number	Yes	No (unless dual SIM)	Yes
Works the moment you land	Yes	No — find a shop first	Yes, instant
Hotspot / tethering	Usually	Usually	Usually

For a remote worker, the eSIM column is the one you want: keep your primary number and WhatsApp alive on your normal SIM, and run data on the eSIM. Dual-line, no compromise.

The catch: device compatibility

eSIM only works on eUICC-equipped hardware. Rule of thumb:

iPhone XS / XR and newer
Samsung Galaxy S20 and newer
Google Pixel 3 and newer

Before you rely on one, it's worth checking your exact model against a device compatibility list. Also watch out for carrier-locked phones — a locked device may reject third-party eSIM profiles. If you travel, buy unlocked.

Practical tips from experience

Install before you fly. Download the profile on home Wi-Fi. Most travel eSIMs only start counting data when you first connect at your destination, so there's zero downside to installing early.
Label your profiles. Phones let you name each line ("Japan trip", "EU data"). Do it — it saves real confusion.
Keep the QR code. If you factory-reset or switch phones, you may need to reinstall the profile.
Think in regions, not just countries. Regional plans (all of Europe, all of Asia) are usually cheaper per GB if you're crossing borders.

Where I get mine

I use PuraSIM — it covers 218 destinations, activation is a one-minute QR scan, and hotspot is included on every plan (which matters when I'm tethering a laptop). Plans start under a dollar, so it's cheaper than a single day of roaming.

Whatever provider you pick, the takeaway is the same: if you work while you travel, stop paying the roaming ransom and stop hunting for SIM shops. Provision once, stay online everywhere.

What's your current travel connectivity setup? Happy to answer eSIM questions in the comments 👇