Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

updated does not match the date displayed in browser #212

Open
dontub opened this issue Apr 9, 2018 · 3 comments
Open

updated does not match the date displayed in browser #212

dontub opened this issue Apr 9, 2018 · 3 comments

Comments

@dontub
Copy link

dontub commented Apr 9, 2018

The value of updated in the app details doesn't match the value displayed in browser. For example for the app used in the documentation (https://play.google.com/store/apps/details?id=com.dxco.pandavszombies&hl=en&gl=us) May 27, 2015 is displayed in browser under Updated, though updated in the app details is set to Feb 27, 2015. What is the meaning of the latter date?

At the mapping path 'ds:3', 0, 12, 8, 0 seems to be the timestamp of the publish date. For the example app it is 1432677999 (2015-05-27 00:06:39).

@facundoolano
Copy link
Owner

facundoolano commented Apr 9, 2018

Thanks for reporting.

Actually the timestamp you show does match the updated:

> new Date(1432677999 * 1000)
Date 2015-05-26T22:06:39.000Z

So we need to use that timestamp for the updated date, and the other for a new field, published date. Ideally we should provide both text and timestamp versions of the date, now that you found they're both available.

@sunnyrty
Copy link

any tempfix ?

@facundoolano
Copy link
Owner

I'm reopening this, since the date in updated seems to be the release date still.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants