Closed Bug 774426 Opened 12 years ago Closed 12 years ago

Nothing shown on about:apps

Categories

(Firefox for Android Graveyard :: Web Apps (PWAs), defect)

16 Branch
ARM
Android
defect
Not set
normal

Tracking

(firefox16 verified, firefox17 verified)

VERIFIED FIXED
Firefox 17
Tracking Status
firefox16 --- verified
firefox17 --- verified

People

(Reporter: wesj, Assigned: wesj)

Details

Attachments

(1 file, 2 obsolete files)

Broken by bug 768276. We're now using the UNIX code here: http://mxr.mozilla.org/mozilla-central/source/dom/apps/src/Webapps.jsm#724 which throws because there's no Home dir on Android.
Attached patch Patch (obsolete) — Splinter Review
There's also an out given in Webapps.jsm, so this is us taking it. Alternatively, we could implement our own isLaunchable implementation?
Assignee: nobody → wjohnston
Attachment #642695 - Flags: review?(mark.finkle)
Filed bug 774422 and bug 774426. I'll mark them as blocking this.
Dang it. Wrong bug.
Blocks: 769712
No longer blocks: 769712
If the existence of the app in the registry (webapps.json) means that the app can always be launchable (i.e., there is no way for the user to remove an app from the OS without Firefox noticing), then yeah this allAppsLaunchable = true is the right thing to use. But you should probably set it to true on the main place where you use Webapps.jsm, which is here if I understand it: http://mxr.mozilla.org/mozilla-central/source/mobile/android/chrome/content/browser.js#5878 (because getSelf/getInstalled/getAll all use that information, and if they happen to be used outside of about:apps they will return empty)
Attached patch Patch v2 (obsolete) — Splinter Review
Thanks felipe! This moves this to browser.js. Works to show apps. There's actually some problems launching them too. Digging in more...
Attachment #642695 - Attachment is obsolete: true
Attachment #642695 - Flags: review?(mark.finkle)
Comment on attachment 642695 [details] [diff] [review] Patch I agree with Felipe, we should set this in WebappsUI.init so we get all the code paths covered. I would also accept a patch to add a simple | return true; | to DOMApplicationRegistry._isLaunchable which has the added benefit of shoving some ANDROID into that file. Maybe we'd get broken less if we made our presence known.
Attachment #642695 - Attachment is obsolete: false
Attachment #642695 - Attachment is obsolete: true
Comment on attachment 642714 [details] [diff] [review] Patch v2 Good enough I guess
Attachment #642714 - Flags: review+
Comment on attachment 642714 [details] [diff] [review] Patch v2 I see this was not ready to review when I collided
Attachment #642714 - Flags: review+
Product: Firefox → Firefox for Android
QA Contact: jsmith → aaron.train
Version: unspecified → Firefox 16
OS: Linux → Android
Hardware: x86 → ARM
Attached patch Patch v3Splinter Review
Threw in a fix for "Add to homescreen here". The other part I was more worried about (launching from an icon) is already fixed on mc apparently. (yay!)
Attachment #642714 - Attachment is obsolete: true
Attachment #642734 - Flags: review?(mark.finkle)
Attachment #642734 - Flags: review?(felipc)
Comment on attachment 642734 [details] [diff] [review] Patch v3 looks ok to me
Attachment #642734 - Flags: review?(mark.finkle) → review+
I think I slightly prefer the fix using allAppsLaunchable = true. _isLaunchable should only be used when you implement a proper way to check if an app has been removed from the home screen (and if you want to stop it from showing in about:apps in that case). there's a `return true` as fallback at the end, so the ifdef fix should be to skip the UNIX part if ANDROID is defined, instead of adding an explicit return true If the motivation to use the ifdef was just to make Android present in that file, don't worry, it won't happen again. And I'll move ifdefs all out of Webapps.jsm soon anyway into WebappOSUtils.jsm which will help with that
I'm more worried about the use of XP_UNIX to determine what to do here. Doesn't seem specific enough. XP_UNIX is apparently defined for anything that isn't Windows or OS/2? http://mxr.mozilla.org/mozilla-central/source/configure.in#8681
Talked to felipe. Since we'd like to eventually remove the #ifdef's here, it seems best just to use the second patch here (with the additional icon fix from the third one). Since mfinkle r+ that originally, I'm just going to push the two and keep talking to felipe about ways to combine/reuse desktop+mobile webapps code as we move forward.
Whiteboard: [qa+]
Attachment #642734 - Flags: review?(felipc)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 17
Looks good. V-F on M-C (Nightly 07/17), GN 4.1.1 Does this need to be uplifted to Aurora?
Status: RESOLVED → VERIFIED
Ping ^
Whiteboard: [qa+]
Comment on attachment 642734 [details] [diff] [review] Patch v3 [Approval Request Comment] Bug caused by (feature/regressing bug #): api spec change done in bug 768276 User impact if declined: fennec can't launch apps from the about:apps dashboard Testing completed (on m-c, etc.): landed on m-c Risk to taking this patch (and alternatives if risky): none, straightforward String or UUID changes made by this patch: none note: what landed is a combination of this patch and patch 1. see comment 15 for the cset
Attachment #642734 - Flags: approval-mozilla-aurora?
Attachment #642734 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Whiteboard: [qa+]
Whiteboard: [qa+]
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: