Closed Bug 942361 Opened 11 years ago Closed 11 years ago

Support dual sim in payments

Categories

(Marketplace Graveyard :: Payments/Refunds, defect, P2)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: andy+bugzilla, Unassigned)

References

Details

When we get to passing the MCC and MNC through to Bango, we need to be sure we get the correct SIM card. We'll be using the SIM card that is assigned for data. The MCC and MCC will be calculated in bugs 941952 and bugs 929232. There should be no changes needed for Bango because header enrichment will use the data SIM as well. See also bug 942355 for matching bugs for the marketplace. Dual SIM support is expected to land in Firefox OS in 1.3. Full docs are here: https://wiki.mozilla.org/FirefoxOS/DSDS
Blocks: 941476
Priority: -- → P2
Blocks: 987661
No longer blocks: 941476
I think we've got this in the MCC/MNC work Stuart has added for Boku. Basically we need to assure that dual SIM works and doesn't break and I saw this in Stuarts pull request.
Assignee: nobody → scolville
What we're doing in bug 987824 is not exactly for dual sim support. It will only apply to the primary sim. Any secondary sim will be ignored which could lead to putting charges on the wrong sim.
(In reply to Kumar McMillan [:kumar] (needinfo for quickness) from comment #2) > What we're doing in bug 987824 is not exactly for dual sim support. It will > only apply to the primary sim. Any secondary sim will be ignored which could > lead to putting charges on the wrong sim. The user selects the primary sim for data in preferences which hence becomes the sim we use in payments. Any other support for dual sims hasn't been planned or scoped. I'd like to have a bug to ensure QA test dual sim against boku payments, so I'm tempted to leave this bug for this and if future work happens for more advanced dual sim support, we'll file bugs for that.
Assignee: scolville → nobody
Based on the fact that we cope with the dual sim with Boku without crashing, I'm closing this. For more complicated scenarios, let's open new bugs.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.