Skip to content
YggdraSIM

Enable / disable / delete

Transition a profile between DISABLED, ENABLED, and ERASED states, and make sure notifications reach SM-DP+ when required.

On this page

Prerequisites

  • a physical or simulated eUICC with at least one installed profile
  • either SCP11/local_access (for direct ES10c) or SCP11/live (for relay-aware handling with notification reconciliation)
  • if relay-aware, the SM-DP+ endpoint must be reachable

Choose the right surface

Goal Surface
State change only, no notification reconciliation needed SCP11/local_access
State change plus automatic HandleNotification to SM-DP+ SCP11/live
Bulk lifecycle orchestration in SGP.32 SCP11/eim_local

Local-access path

[Local SMDPP] > DISCOVER
[Local SMDPP] > ENABLE-PROFILE
[Local SMDPP] > STATUS
[Local SMDPP] > DISABLE-PROFILE
[Local SMDPP] > DELETE-PROFILE

Each command opens its own local SCP11 session. If you need to pick which profile to act on, set the selection beforehand with PROFILE or with the card-aware wizard built into the shell.

Relay path with notification hygiene

python -m SCP11.live --cmd "ENABLE-PROFILE; STATUS; EXIT"

The live shell pulls notifications from the card after the state change and forwards them via HandleNotification, then cleans them off the card. This is important when SM-DP+ tracks lifecycle via notifications.

Validation

After each transition:

python -m SCP11.local_access --cmd "DISCOVER; STATUS; EXIT"

Confirm the expected state is reflected in the listing and that no notifications are left on the card.

Common failures

Symptom Likely cause
Policy rule refused enable PPR on the active profile rejects the transition. Disable the blocking profile first.
No profile selected the shell cannot infer which profile you mean. Pick explicitly.
Notification left on card HandleNotification failed. Re-run the live shell; it reconciles automatically.
Unexpected DISABLED state a prior ENABLE-PROFILE rolled back mid-transaction because a policy rule fired. Check the response log.