I am installing a SMARTY UK eSIM on a Tachyon running particle-tachyon-ril 0.4.5-1. SMARTY requires a separate four-digit confirmation code. The SM-DP+ connection and AuthenticateClient steps succeed, but download ends with status 107 and Prepare download failed (es10b): -50340615 ISDR 127. How can I pass the confirmation code/ePIN? Is there an updated RIL/LPA package or supported lpac method?
Is this going to work? Or should I give up? Thanks.
Thomas was using Vodafone Germany rather than SMARTY UK, but the behaviour is remarkably similar. In both cases:
The download reaches the SM-DP+ server successfully.
Authentication succeeds.
The failure occurs during PrepareDownload (ES10b).
The carrier requires a separate confirmation code (ePIN / 4-digit confirmation code).
The current particle-tachyon-ril-ctl / lpa tooling doesn't appear to provide any mechanism to supply that code.
I also spent some time reverse-engineering the installed /usr/bin/lpa (version 0.1.6). It appears to be a Kigen sample LPA, and I couldn't find any supported mechanism for supplying a confirmation code (no command-line option, no interactive prompt, etc.). I also confirmed that running it directly against the eUICC works using the serial transport, but it still reaches the same ES10b failure.
So my question is:
Does the Tachyon currently support downloading carrier eSIM profiles that require a confirmation code (for example SMARTY UK or Vodafone Germany)?
If the answer is yes:
Is there a newer particle-tachyon-ril or lpa package that supports this?
Or is there another supported provisioning method that should be used instead of particle-tachyon-ril-ctl esim download?
If the answer is no, it would be really helpful to know whether confirmation-code-protected eSIMs are on the roadmap, as I suspect this will affect several European carriers.
Thanks! Hopefully Thomas's findings and mine together help narrow this down.
I've made an eSIM with auth work here in Portugal. Packaging up the patches and instructions, and then I'll send it through. LPA does indeed seem to be the issue.