868910 - [Buri][Shira-48785] Update app error (REGRESSION)

Status: RESOLVED DUPLICATE of bug 869380

(Firefox OS Graveyard :: Gaia::System, defect, P2)

Description

[sync-1]

+++ This bug was initially created as a clone of Bug #447467 +++
 
 Description: 
 
 Update app error (REGRESSION) from marketplace
 
 
  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:
 
 
 AU_LINUX_GECKO_ICS_STRAWBERRY_V1.01.00.01.019.080
 Firefox os  v1.0.1
 Mozilla build ID:20130418070206
 
 ++++++++++ end of initial bug #447467 description ++++++++++
 
 
 
 CONTACT INFO (Name,Phone number):
 
  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

[sync-1]

Created an attachment (id=403311)
 marketplace app UI

Comment 2

[sync-1]

Attachment: marketplace app UI

Created an attachment (id=403311)
 marketplace app UI

Comment 3

[Jason Smith [:jsmith]]

The screenshot seen here is the screenshot capture while an app is loading from a past run. Not necessarily an app error, actually.

Comment 4

[sync-1]

(In reply to comment #3)
 > Comment from Mozilla:The screenshot seen here is the screenshot capture while
 > an app is loading from a past run. Not necessarily an app error, actually.
 > 
 Dear mozilla
 
 1. a past run? The screenshot is not ok when I load it at the first time. After killed marketplace app,  the screenshot is also not ok.
 
 2. update problem? Sometimes the index UI is OK. And we can install applications. But can not entry / use that app after installed.

Comment 5

[Jason Smith [:jsmith]]

Do you have the date of your device set correctly? What's the year set on the device exhibiting this error?

Comment 6

[Daniel Coloma:dcoloma]

This bug is reported with a version from 18th April, a version created during the working week. 

Joe: Can we stop reporting bugs based on versions that old? 
Reporter: Have you tried to repro with a more recent version? (I know you have at least a couple of more recent builds)

Comment 7

[Daniel Coloma:dcoloma]

As it seems we cannot reproduce this bug, and it is based on such an old build I'd suggest we tef- until more details are offered.

Comment 8

[Lukas Blakk [:lsblakk] use ?needinfo]

Removing tef? for now - reporter (or buri.blff) if this can be reproduced with current builds please provide more info in re-nomination as well as a deadline for the milestone/testing date this would have to be fixed by or risk slipping ship dates.

Comment 9

[Amelie Kong]

The bug can be reproduced on latest version if the mobile has invalid date.
As our initial factory date is 2013/1/1, it will not make the certificates work.

refer to Bug869380.
IF we set the date and time as correct time, the market place can work normally and apps can be downloaded.


So we know the root cause, but it is still not good behavior for end user, as he does not know what is the problem when he met this. He will be confused. Espacially for some customer, there is no NITZ available.

Is it possible to change the certificate to cover the 2013/1/1,  or to add some reminder popup for end user to inform him the certificate is wrong?

Comment 10

[Jason Smith [:jsmith]]

In that case, this is a dupe of bug 869380.

As for the bad cert error handling, that's out of scope for 1.01. It's fixed on 1.1, however.