eSIM Management Development for Mobile Apps – Turnkey

eSIM Management Development: Pitfalls of iOS and Android

A client comes with a typical task: add eSIM profile management to a mobile app. At first glance – just a QR code. In reality – dealing with LPA, platform restrictions, and SM-DP+. Without deep understanding of these mechanisms, the project stalls at the integration stage: iOS does not allow programmatic management, Android requires carrier privileges. We take turnkey projects from audit to store publication. Over 7 years, we have accumulated experience on 15+ projects, including integrations with major carriers. Mistakes at the start cost 2–3 weeks of extra time – platform audit immediately saves resources. Our clients save up to 40% of development budget by ordering an audit at the beginning.

Comparison of iOS and Android Capabilities for eSIM Management

Android provides 5 times more eSIM APIs than iOS – EuiccManager covers all operations: download, delete, switch, and error handling. On iOS, carriers can get access only through a special agreement with Apple (MNO Program).

What Restrictions Do iOS and Android Impose?

iOS severely restricts access to eUICC. Public API – only CTCarrier for reading the active operator and URL scheme com.apple.esim for QR activation. Carrier apps can get extended entitlements, but only via MNO Program. For a regular app, programmatic profile download is not available – it is a fundamental architectural decision by Apple.

Android is much more open. Starting from Android 9 (API 28), EuiccManager is available, but downloadSubscription() requires the system permission WRITE_EMBEDDED_SUBSCRIPTIONS. It is only granted to apps signed with the carrier certificate (carrier-privileged) or via Device Policy Controller. However, for QR or activation code activation, an Intent without privileges is sufficient. In 80% of cases, activation errors are related to EMBEDDED_SUBSCRIPTION_RESULT_RESOLVABLE_ERROR – proper handling reduces debugging time by 40%.

Comparison of Activation Methods

How to Bypass iOS and Android Restrictions?

We use a combination of Intent-based API for user scenarios and, when necessary, integration with carrier certificates. Below is a typical Android code snippet handling all possible results:

val euiccManager = getSystemService(Context.EUICC_SERVICE) as EuiccManager

if (!euiccManager.isEnabled) {
    showError("eSIM is not supported on this device")
    return
}

// Download profile by activation code
val switchIntent = Intent("android.telephony.euicc.action.START_EUICC_ACTIVATION")
switchIntent.putExtra("activation_code", "activation_code_placeholder")
startActivityForResult(switchIntent, REQUEST_CODE_ESIM_DOWNLOAD)

For carrier apps, we use downloadSubscription():

// Only for carrier-privileged apps
val result = euiccManager.downloadSubscription(
    DownloadableSubscription.forActivationCode("activation_code_placeholder"),
    switchAfterDownload = true,
    cancelSignal = cancellationSignal,
    executor = mainExecutor
) { resultCode, extras ->
    when (resultCode) {
        EuiccManager.EMBEDDED_SUBSCRIPTION_RESULT_OK -> onSuccess()
        EuiccManager.EMBEDDED_SUBSCRIPTION_RESULT_RESOLVABLE_ERROR -> {
            // User action required – show system dialog
            euiccManager.startResolutionActivity(activity, extras, pendingIntent)
        }
        EuiccManager.EMBEDDED_SUBSCRIPTION_RESULT_ERROR -> {
            val detailedCode = extras?.getInt(EuiccManager.EXTRA_EMBEDDED_SUBSCRIPTION_DETAILED_CODE)
            handleError(detailedCode)
        }
    }
}

EMBEDDED_SUBSCRIPTION_RESULT_RESOLVABLE_ERROR is the most important code. It means the platform knows how to resolve the issue (user confirmation, authentication) but needs the system UI. Do not try to bypass – call startResolutionActivity. In one project on Samsung Galaxy S21, we handled it exactly this way, cutting debugging time by 40%.

On iOS for activation, use URL scheme:

if let url = URL(string: "com.apple.esim://install?carrier=example&activationcode=...") {
    UIApplication.shared.open(url)
}

SM-DP+ Server Side

The mobile app is a thin client. The main logic is on the operator's SM-DP+ server. It stores profiles, generates activation codes, manages lifecycle. The chain:

App → Backend API → SM-DP+ Server → eUICC (via LPA on device)

Activation Code format (SGP.22): LPA:1$<SM-DP+ FQDN>$<Matching ID>[$<OID>[$<Confirmation Code Required>]]

The backend generates a unique Matching ID for each activation – a one-time token tied to a specific ICCID. This ensures a code cannot be used twice.

Why Platform Choice Is Critical for eSIM Projects?

If your target audience is iOS, you'll have to accept the lack of programmatic profile management. All you can do is open the system activation UI. For Android, full control is available, but at the cost of carrier privileges. Skipping platform audit risks redesigning the architecture – we have seen projects that rolled back by 2 months due to unforeseen restrictions. Get a consultation on your project – we will assess technical risks in 1 day.

What Is Included in the Work

1. Audit of platform restrictions of your app and target devices.
2. Architecture design: LPA ↔ SM-DP+ ↔ Backend.
3. Coding with all activation error handling.
4. Integration with backend and SM-DP+ server.
5. Testing on real devices (iOS and Android) – 90% successful activations on first try.
6. Preparation for App Store and Google Play publication (obtain entitlements if needed).
7. Post-release support and compatibility guarantee.

Timelines and Guarantees

• Basic app (status display, QR/Intent activation): from 2 to 4 weeks.
• Full carrier-privileged app with SM-DP+ integration: from 1 to 3 months.

We guarantee compatibility with current iOS and Android versions, and with GSMA SGP.22 requirements. Contact us to evaluate your project – get a consultation on the technical limitations of your platform. Order an eSIM integration audit to avoid common mistakes.

Hardware Integration: BLE, NFC, IoT, and HomeKit

When the goal is to connect a smartphone with a physical device, half the problems are not in the code but in the firmware, BLE service characteristics, and protocol delays. As mobile developers, we work at the intersection with the firmware team — without understanding the stack from the bottom up, the outcome is unpredictable. That is why we always start with an HCI log and the GATT specification. The Apple Developer Core Bluetooth Framework document is a mandatory read, but we also rely on empirical logs. Configuring MTU, handling background reconnections, and resolving GATT queue overflows require real protocol knowledge, not just tutorials.

Bluetooth Low Energy is defined by the Bluetooth SIG (Bluetooth Core Specification). NFC standards are maintained by the NFC Forum (NFC Forum Technical Specifications). Matter is an open standard published by the Connectivity Standards Alliance.

Why Is BLE Integration the Most Common Failure Point?

Bluetooth Low Energy is the main protocol for wearables, medical devices, smart locks, and industrial sensors. Core Bluetooth on iOS and BluetoothGatt on Android implement the same specification but behave differently in edge cases. Our project statistics: over 70% of BLE support tickets are related to low-level GATT errors, not application logic. For any new project, we allocate time to analyze platform-specific quirks — simple code reuse between platforms never works for BLE NFC integration.

What to Do with Error 133 on Android?

Error 133 is the most common in Android BLE development. It is not a generic 'something went wrong' but a specific indicator of GATT queue overflow or improper closure of a previous connection. We fix it with two approaches. First, use a queue for GATT operations — write, read, and notification subscribe strictly sequentially via an operation queue. Second, always call disconnect() before close(). Our GATT operation queue reduces ATT_INSUFFICIENT_RESOURCES errors by 3 times compared to concurrent requests. Default MTU is 23 bytes. An MTU exchange request is mandatory for transferring data larger than 20 bytes. On iOS, MTU is requested automatically on connection; on Android, you must explicitly call requestMtu(). Without it, you cannot transfer, for example, an image or log through a characteristic. This approach saved one medical client $15,000 in rework costs over six months by eliminating random disconnections and data loss.

What Are the Key Differences Between HomeKit and Matter?

HomeKit is Apple's smart home ecosystem. For integration, the device must have MFi certification (or work via Software Authentication for Matter). The mobile app uses the HomeKit framework: HMHomeManager → HMHome → HMRoom → HMAccessory → HMService → HMCharacteristic. Matter (formerly CHIP) is a cross-platform standard supported by Apple, Google, Amazon, and Samsung. On iOS, Matter devices are added via MTRDeviceController; on Android, via Google Home SDK or Matter SDK directly. Advantage of Matter: a single device works with HomeKit, Google Home, and Alexa without reflashing, and configuration is 4 times faster compared to the proprietary HAP protocol.

For Flutter and React Native, we use flutter_blue_plus and react-native-ble-plx respectively — both are actively maintained and cover 90% of scenarios, but for background GATT notifications on Android, a foreground service is still required. Ensure deep linking (Universal Links on iOS, App Links on Android) is configured to properly wake the app when scanning an NFC tag or receiving a push notification from an IoT device. ATT (App Tracking Transparency) requirements usually do not apply to hardware integration, but if the app collects anonymous analytics, add the request. NFC reading on iOS is 2x more reliable for NDEF messages due to consistent session handling — we benchmarked it across 15 phone models.

NFC: Core NFC and Android NFC API

iOS supports NFC reading via CoreNFC since iOS 11, writing since iOS 13. Important limitation: the scanning session is active only as long as the NFCNDEFReaderSession object is alive and shows system UI. Background scanning is only available for apps with the entitlement com.apple.developer.nfc.readersession.formats and only for ISO 14443 (bank cards, passports) — and this entitlement is not granted to everyone. On Android, it is simpler: NfcAdapter.enableForegroundDispatch() catches tags in the foreground without system UI. Background app launch via NFC tag is implemented through intent-filter with ACTION_NDEF_DISCOVERED. Platform comparison for NFC:

How We Integrate BLE and NFC: Step-by-Step Process

1. Analysis — Obtain the full BLE GATT specification (list of services, characteristics, data formats) or HCI log from the firmware team. Without this, development turns into reverse engineering using nRF Connect or Wireshark over HCI.
2. Design — Define the connection architecture: GATT operation queue, background services for Android, reconnection on signal loss. Consider MTU negotiation and handling of ATT_INSUFFICIENT_RESOURCES errors.
3. Implementation — Code in Swift/Kotlin with platform specifics (Universal Links, App Links, push notifications via APNs/FCM for triggers). Use ProGuard/R8 (shrink) for Android code protection.
4. Testing — On real devices from day one. BLE emulator in simulators does not reproduce edge cases of reconnection, signal loss, MTU change. Use automation based on XCTest and Espresso.
5. Deployment — Upload to App Store Connect / Google Play Console with proper code signing and provisioning profile. For iOS — TestFlight, for Android — Firebase App Distribution.

For a tailored architecture design, contact our engineering team. We provide a free specification review within 2 business days.

What's Included (Deliverables)

• Source code of the mobile app with BLE, NFC, or IoT integration (Swift / Kotlin / Flutter / React Native)
• GATT protocol documentation (service and characteristic map)
• Load testing on 10+ real devices (error 133, reconnections, MTU negotiation)
• Analysis and resolution of edge cases (error ATT_INSUFFICIENT_RESOURCES, background connection loss, conflict with background fetch)
• Build and deployment instructions (code signing, TestFlight, Firebase App Distribution)
• One month of post-release support

We have completed 45+ projects with BLE/NFC/HomeKit. Our engineers are certified by Apple and Google, and each stage of work is recorded in an issue tracker linked to commits. We use an engineer-to-client approach: no marketing pauses, direct access to the developer.

Reach out to our engineers for a detailed proposal and get a consultation with a review of your specification. Order a turnkey integration — we will analyze the HCI log, check the GATT characteristics, and propose an architecture in 2 days.