Displaying also test profiles in the list #40

Closed
opened 2024-08-01 10:11:30 +02:00 by valentfr · 4 comments

Are test profiles explicitly filtered by the app in latest version? Would be possible to display test profiles as well?

My usecase is following: I received GSMA consumer eUICC with pre-installed & enabled GSMA TEST profile.
Commercial eSIM profile was loaded succesfully (and listed, see jpg) but it cannot be activated, because GSMA TEST profile is not disabled yet and I cannot proceed with that.

Are test profiles explicitly filtered by the app in latest version? Would be possible to display test profiles as well? My usecase is following: I received GSMA consumer eUICC with pre-installed & enabled GSMA TEST profile. Commercial eSIM profile was loaded succesfully (and listed, see jpg) but it cannot be activated, because GSMA TEST profile is not disabled yet and I cannot proceed with that.

Normally (only operational profiles), enabling the new eSIM profile would automatically disable the old profile.

However, GSMA SGP.22 v2.5 Sectin 5.7.16 explicitly states "verify ... if the target profile is (another Test profile); if any of these verifications fail, terminate the command with an error".

So if a test profile is enabled, you can only enable other test profiles. If you want to switch to operational, you need to explicitly disable the test profile before enabling the operational profile!

Normally (only operational profiles), enabling the new eSIM profile would automatically disable the old profile. However, GSMA SGP.22 v2.5 Sectin 5.7.16 explicitly states "verify ... if the target profile is (another Test profile); if any of these verifications fail, terminate the command with an error". So if a test profile is enabled, you can only enable other test profiles. If you want to switch to operational, you need to explicitly disable the test profile before enabling the operational profile!

I am not sure what the original rationale for hiding test profiles is. But I think the following two approaches would work while keeping that rationale:

  • if the currently enabled profile is a test profile, include it in the list. This way, a user can disable it explicitly, as required by SGP.22
  • add some preference that decides whether test profiles should normally be shown. The default would be to hide the test profiles, retaining the original behaviour
I am not sure what the original rationale for hiding test profiles is. But I think the following two approaches would work while keeping that rationale: * if the currently enabled profile is a test profile, include it in the list. This way, a user can disable it explicitly, as required by SGP.22 * add some preference that decides whether test profiles should normally be shown. The default would be to hide the test profiles, retaining the original behaviour

I am not sure what the original rationale for hiding test profiles is. But I think the following two approaches would work while keeping that rationale:

  • if the currently enabled profile is a test profile, include it in the list. This way, a user can disable it explicitly, as required by SGP.22
  • add some preference that decides whether test profiles should normally be shown. The default would be to hide the test profiles, retaining the original behaviour
I am not sure what the original rationale for hiding test profiles is. But I think the following two approaches would work while keeping that rationale: * if the currently enabled profile is a test profile, include it in the list. This way, a user can disable it explicitly, as required by SGP.22 * add some preference that decides whether test profiles should normally be shown. The default would be to hide the test profiles, retaining the original behaviour

I thought we already had the discussion - and indeed this is a duplicate of #30 from 3 months ago.

I thought we already had the discussion - and indeed this is a duplicate of #30 from 3 months ago.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: PeterCxy/OpenEUICC#40
No description provided.