Closed
Bug 995534
Opened 11 years ago
Closed 11 years ago
APK Factory service reports latest version of MessageMe app as out-of-date
Categories
(Marketplace Graveyard :: Integration, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: myk, Assigned: ozten)
References
Details
The APK Factory service reports the latest version of the MessageMe app as out-of-date:
> wget https://controller.apk.firefox.com/application.apk?manifestUrl=http://chat.messageme.com/manifest.webapp -O messageme.apk
…
> aapt dump --values badging messageme.apk
package: name='com.messageme.chat.p50806838af32cef5b7fde86740d11594' versionCode='1394215728' versionName='1.0'
…
> curl --data '{"installed":{"http://chat.messageme.com/manifest.webapp":1394215728}}' --header "Content-Type:application/json" https://controller.apk.firefox.com/app_updates
{"outdated":["http://chat.messageme.com/manifest.webapp"]}
(I suspect some other apps are affected, but I don't have solid proof.)
Assignee | ||
Comment 1•11 years ago
|
||
I can reproduce this locally. The issue is that my database has version=1397246908 but the apk stored on S3 is version=1397246982
I'll write a script to do this against thousands of APKs and see what % have this 'always out of date' issue.
A couple areas to investigate:
* Known concurrency bug#976170
* multiple deployments using same S3 config
* ???
Assignee | ||
Comment 2•11 years ago
|
||
On stage release, a random group of 78 Apps, 3 had a mismatch between the versionCode in the APK and the version number in the db.
Assignee | ||
Comment 3•11 years ago
|
||
Against production release, 58 apps, 0 had a mismatch.
(I want to run more to get better statistics, but this is a rough estimate of severity).
Assignee | ||
Comment 4•11 years ago
|
||
I've proposed we move stage/production to a single controller in an email thread outside of this bug.
Root cause is bug#976170
Depends on: 976170
Updated•11 years ago
|
Assignee: nobody → ozten.bugs
Priority: -- → P2
Assignee | ||
Comment 6•11 years ago
|
||
This affects at least 10 more OWA as noted in bug#998366 comment#1.
Assignee | ||
Comment 7•11 years ago
|
||
This is fixed.
Expected behavior:
* next update ping, an update is detected
* 2nd update ping, no change. Client will send version as 1398110556
curl -v -H "Content-Type: application/json" -X POST -d '{ "installed":{"http://chat.messageme.com/manifest.webapp":1398110556}}' https://controller.apk.firefox.com/app_updates
{"outdated":[]}
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•