Release Management/Mobile Publishing Documentation

Publishing Fennec

• These instructions assume you're going to upload the android armv7, and android-x86 multi apks. (For T-Store releases, you also need 'ko' apk as well.)
• Use a checkout as some steps are automated. Be sure to use the latest update.
• Download all three multi apks (get_apk.sh script):

./get_apk.sh $version_number # eg: 22.0b5; use --help for more

• From version 32, armv6 are no longer built. For previous version, get_apk.sh will download armv6 if the build is available.
  • (e.g. fennec-22.0b5.multi.android-arm.apk)
  • (e.g. fennec-22.0b5.multi.android-i386.apk)

Play Store

IMPORTANT - Make sure to follow instructions!

• visit https://play.google.com/apps/publish
• From the ALL APPLICATIONS tab (tabs on left), choose "Firefox Beta" or "Firefox"
• To the left of the application title there is an sidebar with an "APK" option, select "APK", then 'Upload new APK to Production'
  • NOTE: The order of uploading no longer matters, PROVIDED THAT all the version codes are different. Activating is done in bulk at the end.
• Click "Browse files" and select the android-x86 multi apk that you downloaded. The file will begin uploading immediately.
  • When it finishes uploading, verify VersionCode is the [truncated] build date, plus 1
  • Hit "Save draft"
• Click "Browse files" and select the android (armv7) multi apk that you downloaded. The file will begin uploading immediately.
  • When it finishes uploading, verify VersionCode is the [truncated] build date.
  • Hit "Save draft"
• Verify that there are 6 APKs listed as current. The three new APKs are not live yet, and have a "Delete" action (in the "Move" dropdown beside them) which you can use if you uploaded the wrong version. There will be warnings about users only getting the newer APK because more than one APK is active. This is normal.
• Click the "Deactivate" Action button for the old android-x86 apk. The android-x86 apk will have a versionCode one higher than the android apk and supports "Native platforms: x86." The new APK will automatically be activated.
• Click the "Deactivate" Action button for the old android (armv7) apk. The android (armv7) apk supports "Native platforms: armeabi-v7a." The new APK will automatically be activated.
• NOTE: Your changes still are *not* live. Make sure you don't see any errors, and click the "Publish Now" button. (You should still see no errors.)
  • a "Warning: Active APKs support fewer devices than previously active APKs. Some users will not receive updates." is expected.
• If this is a beta 1, check to see if any version-specific URL's need updating:
  • note: the URLS may not be present in the text field. Don't worry if they are not.
  • go to "Store Listing" tab -> Recent Changes text field, change the url to http://www.mozilla.com/en-US/mobile/{VERSION}beta/releasenotes/ if it exists.
  • change the system requirements url in Description text field to https://www.mozilla.org/mobile/{VERSION}beta/system-requirements/ if it exists.
  • Note that {VERSION} is something like 21.0
  • and hit "Save"

Note: you can verify that the correct version code is being offered to device owners by viewing the main page for the product:

• Pro Tip: revisit https://play.google.com/apps/publish in another tab, and navigate to the APK's. Make sure the correct versions are listed. (This catches a "forgot to hit publish" error.)
• after some time (up to 75 minutes) you can also check via these links for end user experience:
  • Firefox Beta
  • Firefox Browser for Android (release)

It usually takes about 75 minutes for the new product to appear as available in Google Play.

Yandex Store

Final release builds should be uploaded to Yandex. Betas do not need to be uploaded to Yandex.

• Download the armv7 & i386 multilocale APKs from FTP.
• Login to the Yandex console through https://developer.store.yandex.com
• Click on "Firefox Browser for Android"
• Click on "Upload build", and choose one of the APKs you downloaded from FTP. The build should appear in the "Active builds" section. Repeat for the other apk. (see troubleshooting if upload doesn't work)
• Deactivate the old builds
• Click "Apply"

The application will now be awaiting Yandex moderation but will be automatically live once it passes that step.

Troubleshooting

Sometimes the upload fails at 99% with "unknown error" and all we know is that waiting and trying again the next day (or the next, etc) it might work. E.g. the 35.0 release was able to upload on the day after release without issue. So it's their site's problem and since we don't have a ton of users there, the delay is not a blocker. Just make a note to yourself to go try again the next day.

T Store

Final release builds should be uploaded to T-store. Betas do not need to be uploaded to T-store.

• Download the armv7 "ko" APK from FTP.
• Login to the T store through http://dev.tstore.co.kr/devpoc/main/main.omp
• Click "App" (above "Logout")
• Click "Firefox Browser for Android"
• Click "New APK"
• Click "Upload New Binary" THEN Click "Update Existing Binary" in popup window
• Verify prior binary listed in popup, then click "Update"
• Select the "ko" APK you downloaded earlier, and click "Submit"
• Click "Ok", upload status will be displayed (barber pole)
• Verify that the APK name matches the one you just uploaded
• Click "Request for Review" at top of form, then "OK". Fill out as follows:
  • choose "publish immediately after review"
  • DO NOT put text in the "Recent Changes What's New" box (viewable to customers)
  • put link to release notes www.mozilla.org/mobile/notes/ in the "Reference for Review Notes" section.
• To SAVE and end the publishing process Click "Request for Review" at top of page
• logout