Hi again,
I've spent quite a bit more time investigating this and I think I've found another user hitting what appears to be the same issue:
https://community.particle.io/t/issues-provisioning-esim-following-latest-instructions/69652
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/lpatooling 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-rilorlpapackage 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.