Confirm update experience post HC EOL

RESOLVED FIXED

Status

()

Firefox for Android
Build Config & IDE Support
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: Margaret, Assigned: liuche)

Tracking

Trunk
All
Android
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
We need confirmation of the update experience when honeycomb is longer supported (ie when honeycomb support is removed and we still have two APKs uploaded to the Play store: GB-only and other). Will users on HC post EOL:

* Receive Ginberbread builds as an update?
* No longer receive any updates and Firefox remains on the device?

To test this, we should make test builds before/after the patches from bug 1155801, then upload them to a test account on the Play store.

Richard, is there anything I'm missing here? Have we done this in the past? Is there a test account we should be using, or will a personal account suffice?
Flags: needinfo?(rnewman)
Bug 1155801 Comment 35 has some pointers.

We have a MoCo test account we can use; I flagged Sylvestre for that purpose, but some of us have permissions to write to it.

You can also use your own Play account, but you have to be very careful not to include any Mozilla or Firefox branding (name or icon), or Google will suspend your application before you can test. Don't ask me how I know.

You might find it easier to produce a 21+ APK instead of 14+ for testing, because then you'll be able to test with much more common devices -- find a typical ICS-KK device instead of a Honeycomb tablet!
Flags: needinfo?(rnewman)
(Reporter)

Comment 2

2 years ago
Chenxia said she would look into this.
Assignee: nobody → liuche
I just found this official article about Google Play filters
http://developer.android.com/google/play/filters.html

> maxSdkVersion
> Deprecated. Android 2.1 and later do not check or enforce the maxSdkVersion attribute,
> and the SDK will not compile if maxSdkVersion is set in an app's manifest. For devices
> already compiled with maxSdkVersion, Google Play will respect it and use it for filtering.
> Declaring maxSdkVersion is not recommended. For details, see android:maxSdkVersion.

According to this Google play will follow maxSdkVersion and Honeycomb user should not be able to see or install the app (of course we should still test). However the deprecation is worrisome. In the future we probably should try to avoid having gaps in the list of supported SDK versions - if possible.
Something is tied up with getting Play Store access, but as soon as I get that I'll make a build and try this out.
(In reply to Sebastian Kaspari (:sebastian) from comment #3)

> According to this Google play will follow maxSdkVersion and Honeycomb user
> should not be able to see or install the app (of course we should still
> test). However the deprecation is worrisome.

Note that it's mostly the on-device parts of maxSdkVersion that are deprecated, and it's been this way for years. I don't see how they'd remove the Play filtering without breaking the world, so I'm not super worried.

Some history for this is in Bug 1120762 (testing), Bug 1042382 (the manifest), and of course Bug 1039789.

In particular, the changeset that first specified maxSdkVersion:

https://hg.mozilla.org/mozilla-central/rev/153a8b79e121


> In the future we probably
> should try to avoid having gaps in the list of supported SDK versions - if
> possible.

I agree with that -- Gingerbread just happens to be a special and unique pain-snowflake.
Status: NEW → ASSIGNED
OS: Unspecified → Android
Hardware: Unspecified → All
Version: Firefox 35 → Trunk
Sorry for dropping the ball on this, I'll do this as soon as I get some more specific Play store privs for creating/modifying Android apps for the account.
You should have enough permissions now. Let me know if this is not enough.
I've submitted our current app to the Play Store, and it's pending publishing now. I'll upload another build with the EOL changes and then test the behavior.
I confirmed tha Honeycomb devices do not get any updates (GB or otherwise) after an EOL build with bug 1155801 patches.

Steps I took to test this:
- Create non-debug builds for both r9-10 (Gingerbread-only legacy build) and 11+ (modern build), sign them, upload them to the Play Store
- Download this test build (Firefox test HC deprecation) on a Honeycomb device, as well as a KitKat device, verify that they both work. Turn off auto-update
- Make non-debug builds with the patches from bug 1155801 applied, for both r9-10 and 14+, sign them, and upload them to the Play Store
- Verify that the KitKat device receives and update notification, confirm that the Honeycomb device does not receive an update, and also does not show the test build anymore as an available build

I'm going to turn off the test build now.
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.