Help! I can't get the eSIM to work using the provider's app

Hello everyone,

I’m trying to set up the eSIM via simyo.nl. According to Simyo, the process only works with the Simyo app, but it keeps getting stuck on ‘Iodé’. I receive the verification code by email, enter it, but then the app gets stuck on “Momentje alsjeblieft…” If I understand correctly, then the app installs the eSIM. The alternative methode is to transfer 1 cent via IDEAL, but if the 1 ct is transfered, the banking app opens the simyo app en the waiting screen appears again and stays.

I’ve enabled all supported links in the app settings for both the banking app and the Simyo app, so that’s not the issue. I asked the Simyo helpline for a QR code. The reply was disappointing: “Unfortunately, it is not possible to send an eSIM QR code separately. The eSIM can only be installed with Simyo via the My Simyo app on a compatible device. This is a security measure and applies to all customers.”

Is there a way to resolve this?

I checked logcat – the issue appears to be the same as this issue reported a while ago in Graphene OS (eSIM activation fails from multiple carrier apps · Issue #3794 · GrapheneOS/os-issue-tracker · GitHub): the app waits for a confirmation popup from OpenEUICC, which is not allowed to be triggered by the esim-carrier app, and thus never appears on screen.

03-16 12:54:07.252  1438 12211 D CoreBackPreview: Window{3f6a8a9 u0 nl.simyo.mijnsimyo/nl.simyo.mijnsimyo.flutter.view.FlutterFullScreenActivity}: Setting back callback OnBackInvokedCallbackInfo{mCallback=android.window.IOnBackInvokedCallback$Stub$Proxy@f4f3678, mPriority=0, mIsAnimationCallback=true, mOverrideBehavior=0}

03-16 12:54:08.322 14293 14293 D FLUTTER ESIM DEBUG: DOWNLOADING SUBSCRIPTION...
03-16 12:54:08.323 14293 14293 D FLUTTER ESIM DEBUG: SWITCH AFTER DOWNLOAD true
03-16 12:54:08.326 14293 14293 D FLUTTER ESIM DEBUG: DOWNLOADING SUBSCRIPTION...ANDROID 12 CHECK
03-16 12:54:08.326 14293 14293 D FLUTTER ESIM DEBUG: new version
03-16 12:54:08.327 14293 14293 D FLUTTER ESIM DEBUG: DOWNLOADING SUBSCRIPTION...STARTING REQUEST

03-16 12:54:08.333  2729  3108 I EuiccController: isCompatChangeEnabled changeId: 224562872 changeEnabled: true
03-16 12:54:08.337  2729  3108 D EuiccController: Multiple enabled profiles is not supported, return default port index
03-16 12:54:08.337  2729  3108 D EuiccController:  downloadSubscription cardId: 0 switchAfterDownload: true portIndex: 0 forceDeactivateSim: false callingPackage: nl.simyo.mijnsimyo isConsentNeededToResolvePortIndex: false shouldResolvePortIndex:true callerHasAdminPrivileges:false
03-16 12:54:08.338  2729  3108 I EuiccController: Caller can't manage subscription on target SIM or  User consent is required for resolving port index. Ask user's consent first

03-16 12:54:08.356 14293 14293 D FLUTTER ESIM DEBUG: ON RECEIVE
03-16 12:54:08.356 14293 14293 D         : action=download_subscription, resultCode=1, resultData=null, detailedCode=0.
03-16 12:54:08.356 14293 14293 D FLUTTER ESIM DEBUG: RESOLVABLE ERROR
03-16 12:54:08.358 14293 14293 D FLUTTER ESIM DEBUG: resolving error

03-16 12:54:08.364  1438 14281 V WindowManager: DesktopModeLaunchParamsModifier: phase= 0 task=null activity=null desktop mode is not enabled, skipping
03-16 12:54:08.364  1438 14281 V WindowManager: TaskLaunchParamsModifier:phase=0 task=null activity=null display-area-from-source=DefaultTaskDisplayArea@106089900 display-id=0 task-display-area-windowing-mode=1 suggested-display-area=DefaultTaskDisplayArea@106089900
03-16 12:54:08.369  1438 14281 V WindowManager: DesktopModeLaunchParamsModifier: phase= 0 task=null activity=ActivityRecord{200585660 u0 com.android.phone/.euicc.EuiccResolutionUiDispatcherActivity desktop mode is not enabled, skipping
03-16 12:54:08.369  1438 14281 V WindowManager: TaskLaunchParamsModifier:phase=0 task=null activity=ActivityRecord{200585660 u0 com.android.phone/.euicc.EuiccResolutionUiDispatcherActivity t-1} display-area-from-source=DefaultTaskDisplayArea@106089900 display-id=0 task-display-area-windowing-mode=1 suggested-display-area=DefaultTaskDisplayArea@106089900
03-16 12:54:08.370  1438 14281 V WindowManager: DesktopModeLaunchParamsModifier: phase= 3 task=Task{d9186aa #854 type=standard A=10231:nl.simyo.mijnsimyo} activity=ActivityRecord{200585660 u0 com.android.phone/.euicc.EuiccResolutionUiDispatcherActivity t-1} desktop mode is not enabled, skipping
03-16 12:54:08.371  1438 14281 V WindowManager: TaskLaunchParamsModifier:phase=3 task=Task{d9186aa #854 type=standard A=10231:nl.simyo.mijnsimyo} activity=ActivityRecord{200585660 u0 com.android.phone/.euicc.EuiccResolutionUiDispatcherActivity t-1} display-area-from-source=DefaultTaskDisplayArea@106089900 display-id=0 task-display-area-windowing-mode=1 suggested-display-area=DefaultTaskDisplayArea@106089900 inherit-from-source=fullscreen non-freeform-task-display-area display-area=DefaultTaskDisplayArea@106089900 default-portrait freeform-size-mismatch=Rect(314, 763 - 910, 1987)
03-16 12:54:08.372  1438 14281 V WindowManager: DesktopModeLaunchParamsModifier: phase= 3 task=Task{d9186aa #854 type=standard A=10231:nl.simyo.mijnsimyo} activity=ActivityRecord{200585660 u0 com.android.phone/.euicc.EuiccResolutionUiDispatcherActivity t-1} desktop mode is not enabled, skipping
03-16 12:54:08.373  1438 14281 V WindowManager: TaskLaunchParamsModifier:phase=3 task=Task{d9186aa #854 type=standard A=10231:nl.simyo.mijnsimyo} activity=ActivityRecord{200585660 u0 com.android.phone/.euicc.EuiccResolutionUiDispatcherActivity t-1} display-area-from-source=DefaultTaskDisplayArea@106089900 display-id=0 task-display-area-windowing-mode=1 suggested-display-area=DefaultTaskDisplayArea@106089900 inherit-from-source=fullscreen non-freeform-task-display-area display-area=DefaultTaskDisplayArea@106089900 default-portrait freeform-size-mismatch=Rect(314, 763 - 910, 1987)

Reading this GrapheneOS issue, I believe this is an configuration issue in iodeOS, not in OpenEUICC (?).

Can you fix this? Here is the patch that worked for GrapheneOS a while ago:

1 Like

This is very likely operator incompetence. Every time I talk to Simyo (Spain) for support I get different and conflicting answers from their technical team. Keep insisting. I was able to get them to email me a QR code through some insistence. Besides, It is likely illegal for them to force you to install an app. With a QR code, the eSIM should work just fine. Later on you’ll also need to configure an APN, as well as a seperate APN for MMS, which was also a nightmare, but eventually worked once they gave me the correct values.
********************************************************
Mistral AI gave me the following dubious “legal advice”: Never hurts to send these kinds of things on to your provider if you feel they are overstepping their bounds:

In the Netherlands, telecom providers are generally not allowed to require customers to install a specific app as a condition for providing service. The Dutch telecommunications market is governed by the principle of net neutrality, which means that providers may not delay, block, or discriminate against any internet services or applications, nor may they charge extra for access to specific apps or services. The only exceptions are for network management purposes, such as preventing overload or stopping the spread of malicious software, or if a law specifically bans a certain app or service.

Additionally, the Dutch Telecommunications Act and the Authority for Consumers and Markets (ACM) require providers to offer clear information about services and contractual terms, and to respect consumer rights. There is no legal basis for a carrier to make app installation mandatory for access to basic telecom services.

In summary: No, it is not legal for a carrier to require you to install their app in order to provide you with service in the Netherlands, unless there is a specific, legally justified reason (such as a court order or a law banning the service you are trying to access).

******************************************************
Proton’s Lumo gave me a completely contradictory answer :slight_smile:

2 Likes

Hello, thank you for your reply. I’m not a lawyer, but I suspect your interpretation is legally overreaching.

It confuses net neutrality with SIM/eSIM activation and provisioning processes. Net neutrality concerns data traffic – not activation. This obliges providers to treat internet traffic equally. It does not regulate how a provider activates a SIM/eSIM, which tools are used for provisioning. The Dutch Telecommunicatiewet regulates consumer rights, contract information, access to networks, number portability. It does not contain any obligation to offer a specific eSIM installation method (e.g. QR code). And: In the Autoriteit Consument & Markt is no known rule that states this app free registration.

I therefore suspect that your argument doesn’t hold water, and I can only hope for a bit of goodwill, because eSIM with a QR code is the Android standard.

Nor should we forget what the log file reveals: the error isn’t down to the Simyo app, but to OpenEUICC, if I’m not mistaken.

Maby we get the Apps working with each other, that would be easiest.

We agree. I wasn’t arguing that that interpretation was correct, but that merely it might help get Simyo to cough up a QR code. My feeling after personal dealings with the company is that their technical support team (at least the one I have dealt with in Spain) is incompetent or lazy or both, as they have given me different (and conflicting) answers to the same question.

Keep in mind, there are likely hundreds of devices that cannot run their app, such as smart watches, devices using watchOS, Wear OS, ColorOS Watch, HarmonyOS, Windows laptops with eSIM, as well as innumerable routers. I think insisting that they offer you a QR code or manual install method will be better in the long run than installing what is an app likely full of spyware and bloat.

The simyo.nl customer service team were at last very helpful and provided me with the code for an eSIM. It took a while to sort everything out via chat, but it worked in the end.
As I occasionally have to change devices and therefore need a new eSIM, I’d like to use the simyo app. It would therefore be great if we could report a bug. It was obviously an Iode issue, or rather one involving Iode with OpenEUICC (see log).
Could someone report the bug? @rik ?

1 Like