995852 - [Sora]The parameter settings of a via OMA CP provisioned profile are neither fully visible nor editable after installation.

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Gaia::Wappush, defect, P1)

Description

[sync-1]

Firefox OS v1.3
 Mozilla build ID:20140404164003
 
 According to MTR the UI shall give access to all parameter settings.
 Currently it is not possible to edit or remove stored profiles.
 
 MTR-2942 (SoC: Complies)
 		
 
  DEFECT DESCRIPTION:
 
  REPRODUCING PROCEDURES:
 
  EXPECTED BEHAVIOUR:
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
 
  REPRODUCING RATE:
 
  For FT PR, Please list reference mobile's behavior:

Comment 1

[Gabriele Svelto [:gsvelto]]

Could you please provide the contents of the CP message that triggers this problem and a screenshot highlighting what's missing?

Comment 2

[田旻]

(In reply to Gabriele Svelto [:gsvelto] from comment #1)
> Could you please provide the contents of the CP message that triggers this
> problem and a screenshot highlighting what's missing?

The phone can recevie the OMA provesion message about setting  APN, but OMA Provision which is to set a email account can't be received.

Comment 3

[Gabriele Svelto [:gsvelto]]

(In reply to 田旻 from comment #2)
> The phone can recevie the OMA provesion message about setting  APN, but OMA
> Provision which is to set a email account can't be received.

Isn't this a duplicate of bug 972705? If that's the case then this is a new feature and can't block 1.3.

Comment 4

[田旻]

(In reply to Gabriele Svelto [:gsvelto] from comment #3)
> (In reply to 田旻 from comment #2)
> > The phone can recevie the OMA provesion message about setting  APN, but OMA
> > Provision which is to set a email account can't be received.
> 
> Isn't this a duplicate of bug 972705? If that's the case then this is a new
> feature and can't block 1.3.

This bug is not the same as that one. This bug includes the edit attribute, which requires the profile details can be edited after installation on the phone.

Comment 5

[Gabriele Svelto [:gsvelto]]

(In reply to 田旻 from comment #4)
> This bug is not the same as that one. This bug includes the edit attribute,
> which requires the profile details can be edited after installation on the
> phone.

OK, then can you provide the contents of a message that is not working along with a screenshot of the issue? A detailed description of the missing fields would also help.

Comment 6

[Beatriz Rodríguez [:brg]]

Edition of any profile is restricted in current APN architecture to "Custom" profile. Any profile received through OMA CP is considered not editable, like the ones we got from apn.json file. This is a new feature request not supported in 1.3.

Comment 7

[Preeti Raghunath(:Preeti)]

Bruce, Please monitor for new feature

Comment 8

[Beatriz Rodríguez [:brg]]

I guess this issue will be covered once the specs in https://bugzilla.mozilla.org/show_bug.cgi?id=1024776#c5 will be implemented, am I right?

Comment 9

[Bruce Huang [:bhuang] (inactive)]

Yes, the new implementation will still read from the settings DB so it will cover this.

Comment 10

[Juanjo Iglesias]

I have tested using flame master (Gecko 745dcf1, Gaia 9306e43) and flame v2.1 (Gecko 604fdf4, Gaia 7f738ed), in both case the APN profiles can be edited and deleted from the APN list. 

If the APN profile is from default settings or from OMA CP message, in both cases the data can be readed and edited, and the profile can be deleted.

Comment 11

[Beatriz Rodríguez [:brg]]

I mark this bug as WFM because it was covered by the UX refresh in APN done in 2.1 scope. Change resolution if you feel otherwise.
Thanks for fixing it.