Release Management/Mobile Publishing Documentation: Difference between revisions

Jump to navigation Jump to search
play store script
(→‎Play Store: adding a note about staged rollout)
(play store script)
Line 1: Line 1:
= Publishing Fennec =
= Publishing Fennec =
* These instructions assume you're going to upload the android armv7, and android-x86 multi apks.
* These instructions assume you're going to upload the android armv7, and android-x86 multi apks.
* Use a [http://hg.mozilla.org/build/braindump/file/default/releases-related/ checkout] as some steps are automated. Be sure to use the latest update.
* Use a [https://github.com/mozilla-releng/mozapkpublisher/ checkout] as some steps are automated. Be sure to use the latest update.
* Download all three multi apks ([http://hg.mozilla.org/build/braindump/file/default/releases-related/get_apk.sh get_apk.sh script]):
* Download all three multi apks ([https://github.com/mozilla-releng/mozapkpublisher/blob/master/mozapkpublisher/get_apk.py script]):
  ./get_apk.sh $version_number # eg: 22.0b5; use --help for more (exemple: -b for build #)
  ./mozapkpublisher/get_apk.py $version_number # eg: 22.0b5; use --help for more (exemple: -b for build #)
* From version 32, armv6 are no longer built. For previous version, get_apk.sh will download armv6 if the build is available.
**(e.g. [https://ftp.mozilla.org/pub/mozilla.org/mobile/candidates/22.0b5-candidates/build1/android/multi/fennec-22.0b5.multi.android-arm.apk fennec-22.0b5.multi.android-arm.apk])
**(e.g. [http://stage.mozilla.org/pub/mozilla.org/mobile/candidates/22.0b5-candidates/build1/android-x86/multi/fennec-22.0b5.multi.android-i386.apk fennec-22.0b5.multi.android-i386.apk])


== Play Store ==
== Play Store ==
<font color="red">'''IMPORTANT - Make sure to follow instructions!'''</font>
* NOTE: Release version is pushed via Play store Staged Rollout. See [https://support.google.com/googleplay/android-developer/answer/6346149?hl=en Staged Rollout on Production]
* visit https://play.google.com/apps/publish
* From the ALL APPLICATIONS tab (tabs on left), choose "Firefox Beta" or "Firefox Browser for Android"
* 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.
* Publishing APKs (Staged rollout)
** NOTE: Your changes still are *not* live.
** Make sure you don't see any errors, and click the "Publish as staged rollout" (starting at 10% for release version for first 48 hrs) OR "Publish Now" (for beta APKs).  (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  <code>http://www.mozilla.com/en-US/mobile/{VERSION}beta/releasenotes/</code> if it exists.
** change the system requirements url in Description text field to <code>https://www.mozilla.org/mobile/{VERSION}beta/system-requirements/</code> if it exists.
** Note that <code>{VERSION}</code> is something like 21.0
** and hit "Save"


 
python mozapkpublisher/get_apk.py --version $VERSION --build $BUILD
Note: you can verify that the correct version code is being offered to device owners by viewing the main page for the product:
python mozapkpublisher/push_apk.py --package-name org.mozilla.firefox --service-account XXX@developer.gserviceaccount.com --credentials foo.p12 --apk-x86=apk-download/fennec-$VERSION.multi.android-i386.apk --apk-armv7-v15=apk-download/fennec-$VERSION.multi.android-arm-api-15.apk --track rollout --rollout-percentage 10
* 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:
** [https://play.google.com/store/apps/details?id=org.mozilla.firefox_beta Firefox Beta]
** [https://play.google.com/store/apps/details?id=org.mozilla.firefox Firefox Browser for Android (release)]
 
 
'''It usually takes about 75 minutes for the new product to appear as available in Google Play.'''
 
NOTE: If Google Play is not updated within 3-4 hours of updating APKs, go to https://play.google.com/apps/publish, click on Help button on the top right, and then on "live chat" in the pop-up dialogue. You should be able to connect with someone from Google Play Developer Tech Support and request them to investigate why the uploads are not visible yet.


== Yandex Store ==
== Yandex Store ==
Account confirmers, Anti-spam team, Bureaucrats, canmove, Confirmed users, Module owners and peers, smwadministrator, smwcurator, Administrators, MozillaWiki team, Widget editors
731

edits

Navigation menu