Closed
Bug 1066013
Opened 10 years ago
Closed 10 years ago
Initialize appCache path
Categories
(Core :: Networking: Cache, defect)
Tracking
()
People
(Reporter: zoran.jovanovic, Assigned: zoran.jovanovic)
Details
(Whiteboard: [Tako_Blocker])
Attachments
(1 file, 1 obsolete file)
1.30 KB,
patch
|
fabrice
:
review+
fabrice
:
approval-mozilla-b2g34+
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.125 Safari/537.36
Steps to reproduce:
Preload appcache for apps pre-installed to /data partition in FFOS, e.g. with eng build of FFOS.
Actual results:
appCache path on app object not initialized resulting in failed cache installation.
Expected results:
Cache should be installed and apps should load offline.
Assignee | ||
Updated•10 years ago
|
Flags: needinfo?(jonas)
Flags: needinfo?(honzab.moz)
Flags: needinfo?(fabrice)
Sadly I don't know this code.
Flags: needinfo?(jonas)
Comment 3•10 years ago
|
||
We used to set cachePath in gaia's build system when creating the webapps.json file that ends up in /system. Your patch will add an appCache property to all apps even if they don't need it, and so we don't bail out early in OfflineCacheInstaller.installCache() anymore (we exit at !cacheDir.exists() though so it's not too terrible either).
I think we should rather fix updateOfflineCacheForApp() to check if manifest.fullAppcachePath() exists, and if so call OfflineCacheInstaller.installCache({ cachePath: app.cachePath || app.basePath, ... });
Flags: needinfo?(fabrice)
Assignee | ||
Comment 4•10 years ago
|
||
Fixes Fabrice's comments.
Attachment #8487867 -
Attachment is obsolete: true
Attachment #8507060 -
Flags: review?(fabrice)
Updated•10 years ago
|
Attachment #8507060 -
Flags: review?(fabrice) → review+
Updated•10 years ago
|
Whiteboard: [Tako_Blocker]
Comment 5•10 years ago
|
||
[Blocking Requested - why for this release]:
partner would like to have this fix in 2.1, raise 2.1? for triage.
blocking-b2g: --- → 2.1?
Updated•10 years ago
|
Flags: needinfo?(fabrice)
Updated•10 years ago
|
Attachment #8507060 -
Flags: approval-mozilla-b2g34+
Updated•10 years ago
|
Flags: needinfo?(fabrice)
Updated•10 years ago
|
Assignee: nobody → zoran.jovanovic
Comment 7•10 years ago
|
||
hi Bhavana,
since both review+ and uplift approval granted, could you please let me know when it will be uplifted to 2.1?
Flags: needinfo?(bbajaj)
Comment 8•10 years ago
|
||
Comment 9•10 years ago
|
||
(In reply to Francis Lee [:frlee] from comment #7)
> hi Bhavana,
>
> since both review+ and uplift approval granted, could you please let me know
> when it will be uplifted to 2.1?
The patch was not even landed... People need to do diligence to ensure their work ends up in the tree.
Flags: needinfo?(bbajaj)
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla36
Comment 11•10 years ago
|
||
status-b2g-v2.1:
--- → fixed
status-b2g-v2.2:
--- → fixed
status-firefox34:
--- → wontfix
status-firefox35:
--- → wontfix
status-firefox36:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•