In bug 926343, nsIIccProvider is changed to support multi-sim. We may need to handle multi-sim scenario in OperatorApps as well.

I'm looking into the Operator apps for multi-SIM at the moment and am wondering if we could install the operator apps even after first-run in that case. So change first-run to 'first SIM per operator id'. It would become impossible to decide which apps to remove using the current variant mechanism, since the second SIM can be of any operator, which could result in wasted storage.

I believe what you're describing goes against the requisites of the User Story defined by product at bug893800. I'm copying Jorge/Marce in case they have something to add here.

Current approach only takes into account the SIM card inserted in first slot (whatever it means in the device), and customization is only applied the first time to insert a SIM card, then removing remaining apps to save flash memory space. So, it would work OK with a single SIM card, or with two SIM cards of the same operator. I do not know if it make sense for anyone to cover the scenario of two SIM cards of different operators, but for me it is really really weird.

The use case is for multi-SIM devices that are sold on the open market, in that case it is impossible to know if the first SIM inserted is 'your' operator, which currently makes it impossible to still apply customizations, since the customer decided to insert a SIM for a different operator first/in slot 1.

(In reply to Casper van Donderen from comment #4) > The use case is for multi-SIM devices that are sold on the open market, in > that case it is impossible to know if the first SIM inserted is 'your' > operator, which currently makes it impossible to still apply customizations, > since the customer decided to insert a SIM for a different operator first/in > slot 1. Maybe, we can let users select "his" operator in FTE manual like bug 926347.