Failed to download eSIM #3
Loading…
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?
Hello there,
I'm using OpenEUICC on my POCO X3 NFC that runs MIUI by Xiaomi.EU. And I'm using KernelSU.
I'm using 5ber.eSIM. I was trying to delete eSIM profile, and it's working. But when I've wanted to re-add the profile, it's kept have error Failed to download eSIM.
And I was wondering what happened. But there is success try, and when I've tried to do it again, same error happened again.
Maybe this log can help.
Best regards,
What do you mean by re-adding the profile? Most eSIMs cannot be downloaded more than once, and this is the expected behavior if the eUICC server refuses to serve the profile to you (because you have downloaded it successfully before).
It's possible to downloading it more than once (my cellular provider), it's tested with the 5ber.eSIM application. (truphone and go-esim)
Adding (using 5ber.eSIM app) -> delete (using 5ber.eSIM app) -> Adding (using OpenEUICC app) the result is failed.
Adding (using 5ber.eSIM app) -> delete (using OpenEUICC app) -> Adding (using 5ber.eSIM app) the result is success.
And after some testing (adding permissions), it's looks like OpenEUICC app need to have
org.simalliance.openmobileapi.SMARTCARD
permissions. It's run as expected (success).Since both of removable eUICCs are having that permissions.
Both app permissions
\Edit (again): It's seeming doesn't work again after testing with
org.simalliance.openmobileapi.SMARTCARD
permissions, but with the 5ber.eSIM apps, works normally... I don't have any idea again.But, wait, the permissions are gone...
It's gone
I'm sure I've already adding it. Let me try again.
Edit: I did manage to add openmobileapi permissions. But, same, still not working. But when I'm opening the app and the OpenUICC at the same time, it's working well... So, I don't have any idea what's happen, is that possible that there is key something inside the chip on the removable eUICC?
Hi, I am closing this issue because it looks like the problem stemmed from a lack of notification support (as in, the deletion event was never sent to the carrier). This should have been fixed by now on the master branch.