Closed
Bug 991628
Opened 11 years ago
Closed 11 years ago
[Settings][OMA CP] Not possible to select an APN received via OMA CP message if there is already one with the same name
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(blocking-b2g:1.3+, b2g-v1.3 fixed, b2g-v1.3T fixed, b2g-v1.4 fixed, b2g-v2.0 fixed)
People
(Reporter: isabelrios, Assigned: jaoo)
Details
(Whiteboard: [cert])
Attachments
(4 files, 4 obsolete files)
46 bytes,
text/x-github-pull-request
|
Details | Review | |
9.12 KB,
patch
|
arthurcc
:
review+
|
Details | Diff | Splinter Review |
46 bytes,
text/x-github-pull-request
|
fabrice
:
approval-gaia-v1.3+
|
Details | Review |
1.79 MB,
video/3gpp
|
Details |
1.3 04/03 buri build:
Gecko-1bbed3c
Gaia-c5cd3a1
STEPS
Receive an OMA CP message with data APN
Accept it and store the APN
Receive the same OMA CP message again
Accept it again and store the APN
Go to Settings -> Cellular and Data -> Data settings and try to select the second APN received and stored
EXPECTED
It should be possible to select any of the APN stored and listed in Data Settings
ACTUAL
When there are two APNs with the same name, it is not possible to select the second one of the list
Reporter | ||
Updated•11 years ago
|
Summary: [Settings][OMA CP] Not possible to select an APN received via OMA CP message and there is already one with the same name → [Settings][OMA CP] Not possible to select an APN received via OMA CP message if there is already one with the same name
Assignee | ||
Comment 1•11 years ago
|
||
Go for it. I'll fix this bug asap. Thanks.
Assignee: nobody → josea.olivera
Comment 2•11 years ago
|
||
Thanks Jose Antonio.
Bug reported as certification blocker, nominating to 1.3.
blocking-b2g: --- → 1.3?
Updated•11 years ago
|
blocking-b2g: 1.3? → 1.3+
Assignee | ||
Comment 3•11 years ago
|
||
WIP patch.
Assignee | ||
Comment 4•11 years ago
|
||
v1 patch. It still needs tests.
Assignee | ||
Comment 5•11 years ago
|
||
Attachment #8402379 -
Attachment is obsolete: true
Assignee | ||
Comment 6•11 years ago
|
||
Arthur, let me share some background about what is going on here. If a couple or more APNs have the same name (same value for carrier property) there was an issue while switching between those APNs. This patch fixes that issue by using a hash code for the value property for the input element. Could you take a look a it please? I added a test case for the issue, hope it helps.
Attachment #8402572 -
Attachment is obsolete: true
Attachment #8403158 -
Flags: review?(arthur.chen)
Updated•11 years ago
|
Whiteboard: cert
Updated•11 years ago
|
Whiteboard: cert → [cert]
Assignee | ||
Comment 7•11 years ago
|
||
Arthur, just addressed the comment you left in the PR. Thanks. Could you take a look a it again please? Thanks.
PS. PR updated. Feel free to review the patch through it.
Attachment #8403158 -
Attachment is obsolete: true
Attachment #8403158 -
Flags: review?(arthur.chen)
Attachment #8403839 -
Flags: review?(arthur.chen)
Comment 8•11 years ago
|
||
Comment on attachment 8403839 [details] [diff] [review]
v3
Review of attachment 8403839 [details] [diff] [review]:
-----------------------------------------------------------------
The patch looks good to me. The only one concern is that is it possible to use a more sophisticated hash algorithm? The chance of collision may be small but I think it is always good using a more robust method.
Attachment #8403839 -
Flags: review?(arthur.chen)
Assignee | ||
Comment 9•11 years ago
|
||
Function changed. Could you take a look a it again please? Thanks.
Attachment #8403839 -
Attachment is obsolete: true
Assignee | ||
Updated•11 years ago
|
Attachment #8403933 -
Flags: review?(arthur.chen)
Comment 10•11 years ago
|
||
Comment on attachment 8403933 [details] [diff] [review]
v4
r=me, thank you! Please also create a pull request against v1.3 branch for running travis.
Attachment #8403933 -
Flags: review?(arthur.chen) → review+
Assignee | ||
Comment 11•11 years ago
|
||
Updated•11 years ago
|
status-b2g-v1.3:
--- → affected
status-b2g-v1.3T:
--- → affected
status-b2g-v1.4:
--- → affected
status-b2g-v2.0:
--- → affected
Assignee | ||
Comment 12•11 years ago
|
||
Travis passes for both master and v1.3 branches. I tested both patches on peak device and everything seems to work correctly. Gaia master branch patch landed at https://github.com/mozilla-b2g/gaia/commit/5c56b25486e2b9ac438ef9c3a7825ed4445d5b34.
Thanks Arthur!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Target Milestone: --- → 1.4 S5 (11apr)
Comment 13•11 years ago
|
||
Please request approval-gaia-v1.3 when this is ready for uplift.
Flags: needinfo?(josea.olivera)
Target Milestone: 1.4 S5 (11apr) → 1.4 S6 (25apr)
Comment 14•11 years ago
|
||
v1.4: https://github.com/mozilla-b2g/gaia/commit/a859e2d3e7bbc3fd9f33b1a1bdd2b324469586f9
Still waiting on the v1.3 approval request.
Reporter | ||
Comment 15•11 years ago
|
||
Just checked the current behavior on 1.4 today's buri build:
Gecko-3f64d65
Gaia-961f7d4
Now it is possible to select any of the apns with the same name, that is great. But, another issue happens. If there are for example three apns with the same name, and the third of them is selected, if data settings menu is closed and open again, then the first one is selected automatically. Please see video file attached.
Instead of re-opening this bug if you agree I will open a follow up one.
Reporter | ||
Comment 16•11 years ago
|
||
Reporter | ||
Comment 17•11 years ago
|
||
Follow up bug 998914 already open
Comment 18•11 years ago
|
||
(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #14)
> Still waiting on the v1.3 approval request.
Assignee | ||
Comment 19•11 years ago
|
||
Comment on attachment 8404676 [details] [review]
[v1.3] Pointer to Github PR https://github.com/mozilla-b2g/gaia/pull/18172
NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings.
[Approval Request Comment]
[Bug caused by] (feature/regressing bug #): DSDS stuff / bug 962453
[User impact] if declined: If there are some APNs with the same carrier name the user is not able to switch between them.
[Testing completed]: Yes, unit test added too.
[Risk to taking this patch] (and alternatives if risky): Low, in fact this is a corner case. I mean all the APN in the apn.json data base have different names. Only APNs set through OMA client provisioning (CP) could have the same carrier name for all of them and the carrier rarely sends this APNs to the device.
[String changes made]: No changes.
Attachment #8404676 -
Flags: approval-gaia-v1.3?(fabrice)
Flags: needinfo?(josea.olivera)
Updated•11 years ago
|
Attachment #8404676 -
Flags: approval-gaia-v1.3?(fabrice) → approval-gaia-v1.3+
Comment 20•11 years ago
|
||
Updated•11 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•