-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Ship Fenix x86_64 builds #445
Comments
Will wait a few weeks for Fennec Nightly users to test this. 1.5% of Fennec users have it. |
@vesta0 and @pocmo - Fennec Nightly has been shipping x86_64 builds since February 13 (Fennec bug 1505538) without any big problems. Thus Fenix and R-B can start shipping x86 and x86_64 builds whenever you like, so I am removing this issue's Admittedly, we don't have many x86 or x86_64 Fennec Nightly users. Based on telemetry, Fennec Nightly's architecture split is:
|
Fenix x86_64 will need support from Application Services: |
Removing https://maven.mozilla.org/?prefix=maven2/org/mozilla/geckoview/geckoview-nightly-x86_64/ |
This is done. |
@kbrosnan When were Fenix x86_64 builds first available? I don't see them in the Google Play Store. For yesterday's Fenix and Reference Browser releases (both version 1.0.1918), I see only APKs for armeabi-v7a, arm64-v8a, and x86. Maybe we're building the x86_64 APKs but not uploading them to the Play Store yet? |
We need to publish 64-bit builds to the Google Play Store before Google's August 1 deadline requiring 64-bit support (for apps that include native code).
https://android-developers.googleblog.com/2019/01/get-your-apps-ready-for-64-bit.html
It looks like Fenix is only shipping 32-bit ARMv7 and x86 builds:
fenix/.taskcluster.yml
Lines 92 to 93 in 19dd468
GeckoView publishes x86_64 builds in Maven, but we haven't actually shipped x86_64 builds to Fennec Nightly users yet. I'm working with Releng and Relman to ship x86_64 Fennec Nightly by the end of this week.
Fenix will need to ship x86_64 builds by Google's August 1 deadline (or take down our 32-bit x86 builds), but I recommend that you wait for Fennec Nightly users to dogfood x86_64 for a couple weeks before shipping x86_64 Fenix builds. The beginning of Fenix M3 (March) would probably be a good time.
(For shipping ARM64 Fenix builds, see issue #444.)
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: