1048842 - [Loop] Changing the date of the device, change the expiration time of a shared URL

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::Loop, defect)

Description

[mbarone]

Device: Flame / Fire E
Loop Id: 24c7618

STR:
1. Share a URL by email
2. Once the shared URL is shown in the call log (with the expiration time), open settings app and change the date of the device
3. Open again the call log in Loop

ACTUAL RESULT
The expiration time change according the date of the device

EXPECTED RESULT
The expiration time should be independent of the date of the device. Also in this case is possible to call an expired URL.

Comment 1

[Jayme Mercado [:JMercado] (Inactive 3/4/2016)]

This issue still occurs on the latest 2.0 build with the v165 KK base as written for Device B.  When the device date is changed, the expiration time changes as well.

Environmental Variables:
Device: Flame 2.0
BuildID: 20140819030000
Gaia: 287a2c725a5c14e5dc1d48e3158ffc79c7d1ea33
Gecko: 6329352ca531b977979451e77e5862af485388b2
Version: 32.0 (2.0) 
Firmware Version: v165
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0


Loop version: 32219a2

Comment 2

[Borja Salguero [:borjasalguero]]

In this case, the expiration date is a number of days based on the current date. If you change the reference date, the expiration date shown will be updated accordingly (and I think this is the right behavior). Could you explain the STR? Is this a bug?

Comment 3

[Maria Angeles Oteo (:oteo)]

Borja, one question, are we calculating (in the mobile application) the expiration date or the server is providing an absolute expiration date?

Comment 4

[Borja Salguero [:borjasalguero]]

Server provides a date, (for example 1st of December, 2014). Taking server date and the current date (the one we use as reference), we calculate the number of days when we could use the URL. That's why changing the device date (imagine if we set the date to the 2nd of December, 2014) will be translated sometimes in the label 'Expired' in the UI.

Comment 5

[Maria Angeles Oteo (:oteo)]

Thanks Borja!
so if the user sets correctly the date of the device, there should not be any issue. In that case I don't think this bug is blocking.

The only way to avoid this weird behavior should be showing the expired date and not the pending days for the expiration, but this would be a product decision.

Jorge, Romain, up to you, guys!

Comment 6

[Romain Testard [:RT]]

I think this is a fairly edge case and I'm happy to leave this one as is currently (I'd expect my calendar to wrongly warn me of meetings if I set my date incorrectly on my device).
I expect most people use automatic dates and times rather than manual but I may be wrong.

Comment 7

[Maria Angeles Oteo (:oteo)]

(In reply to Romain Testard [:RT] from comment #6)
> I think this is a fairly edge case and I'm happy to leave this one as is
> currently (I'd expect my calendar to wrongly warn me of meetings if I set my
> date incorrectly on my device).
> I expect most people use automatic dates and times rather than manual but I
> may be wrong.

Agree with you, 
Massimo, let me know your opinion to close the bug or not