718435 - "Open" button is disabled after install/update

Status: RESOLVED INVALID

(Firefox for Android Graveyard :: General, defect)

Description

[Camelia Urian]

Attachment: Screen shot

Build ID: Mozilla/5.0 (Android; Linux armv7l; rv:12.0a1) Gecko/20120116 Firefox/12.0a1 Fennec/12.0a1
Device: Samsung Nexus S
OS: Android 2.3

Steps to reproduce:
1. Go to http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-central-android/ and download build.
2. Wait for download to finish.
3. Drop down the system notifications and tap on the "Download complete" notification for Fennec.
4. Select  "Install"
5. Wait for installation to finish.

Expected results:
 User can select "Open" to launch application.

Actual results:
 "Open" button is disabled.

Notes: 
 - User has to select "done" and go to applications to launch Fennec.
 - Same issue is reproducing after upgrade.

Comment 1

[Marcia Knous [:marcia]]

I am seeing this on my phone as well, and I recall it started happening a few days ago. We should try to get a regression range since I believe this is a recent regression. I have a Motorola Photon running 2.3.4.

Comment 2

[Aaron Train [:aaronmt]]

I'm guessing this happens with standard Android behaviour when you introduce multiple activities deployed during install; so the 'Open' isn't tied to one activity. Sync was just introduced and that is why you are probably seeing this. I'm guessing the AndroidManifest was tweaked to include the activities for Sync [1].

D/PackageManager( 2715):   Activities: org.mozilla.fennec.App org.mozilla.fennec.Restarter org.mozilla.gecko.sync.setup.activities.SetupSyncActivity org.mozilla.gecko.sync.setup.activities.AccountActivity org.mozilla.gecko.sync.setup.activities.SetupFailureActivity org.mozilla.gecko.sync.setup.activities.SetupSuccessActivity org.mozilla.fennec.CrashReporter org.mozilla.fennec.LauncherShortcuts org.mozilla.gecko.AwesomeBar org.mozilla.gecko.TabsTray org.mozilla.gecko.GeckoPreferences

[1] http://hg.mozilla.org/mozilla-central/diff/81d34a32e031/mobile/android/base/AndroidManifest.xml.in

This same behaviour happens with any application with multiple activities (or launcher shortcuts).

Probably a WONTFIX based on this.

Comment 3

[Camelia Urian]

Not reproducible on:
Mozilla /5.0 (Android;Linux armv7l;rv:12.0a1) Gecko/20120114 Firefox/12.0a1 Fennec/12.0a1
http://hg.mozilla.org/mozilla-central/rev/3eaa7d9f1c69

Reproducible on:
Mozilla /5.0 (Android;Linux armv7l;rv:12.0a1) Gecko/20120115 Firefox/12.0a1 Fennec/12.0a1
http://hg.mozilla.org/mozilla-central/rev/21c84409902e

Regression range:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=3eaa7d9f1c69&tochange=21c84409902e

Comment 5

[Lawrence Mandel [:lmandel] (use needinfo)]

I see that this has been resolved as invalid but this reads like a completely valid bug to me. It is unexpected behaviour that Firefox can't be launched with the open button after it is installed. Is there any way to specify a default activity in the manifest? Is there any other way to work around this issue?

At the very least I think this bug should be resolved as wontfix instead of invalid.

Comment 6

[Brad Lassey [:blassey] (use needinfo?)]

I'm assuming it was resolved invalid because the installer is part of the OS, not its not really our bug.

Comment 7

[Lawrence Mandel [:lmandel] (use needinfo)]

Well, I don't see this problem with other apps. It's our apk that's causing the open button to be disabled.