it is recommended to support ePIN input. #59
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
it is recommended to support ePIN input. When downloading the Germany Vodafone eSIM, you need to enter the ePIN. enter the ePIN into the confirmation code, but the download fails, once a download fails, it cannot be downloaded again from other devices.
There's nothing called the ePIN in the eUICC standard. If ePIN just means confirmation code, then something else must have caused the download failure. In that case logs are required to diagnose why.
I have the same problem with vodafone de. Failed to download profile. See log
below is the log after I failed to download Vodafone eSIM through OpenEUICC, please check and fix, thank you!
The problem is that these logs tell me nothing other than the download was refused. Is there more information on what ePIN actually is?
ref: https://www.vodafone.de/hilfe/alles-zur-esim.html#was-ist-der-esim-aktivierungscode-die-epin-und-die-eid
ePIN = Confirmation Code
however, the Vodafone eSIM can be downloaded normally using 5ber eSIM cards and apps, but they are rejected when using OpenEUICC. This should be a bug in the program. Please check and test.
@dream I have no way to test the Vodafone eSIM, but: the latest OpenEUICC release has a better download flow with more detailed error diagnosis on failure. Would you mind testing that out and see exactly what it says about that failure?
The log given above does tell me it failed at
authenticateClientto Vodafone's SM-DP+ server, but it didn't contain the exact error code returned by the server. Please either enable verbose logging or use the latest OpenEUICC/EasyEUICC release with its error diagnosis, which will tell me exactly what went wrong.Data sent to the SM-DP+ server at or before
authenticateClientincludes only the eUICC's own info plus the matching ID ("activation code") and IMEI. Confirmation code (ePIN) isn't even sent at that step.So for that to fail, it means the server either doesn't like the eUICC you're using, or the matching ID (activation code) is wrong, or the server expects to have an IMEI. If it is really due to a missing IMEI though, I don't understand how 5ber's app would be able to download it, since unprivileged apps can't access IMEI anymore on Android. Maybe the server just expects some IMEI, not a valid IMEI, or the IMEI of the device itself?
There's also a possibility that our matching ID encoding is broken by passing from Java -> JNI. Is the activation code provided by Vodafone purely alphanumerical or does it contain other special characters?
ref: #137
This seems to be mostly superseded by #137, closing in favor of that.