"Fossies" - the Fresh Open Source Software Archive
Member "firefox-69.0.1/taskcluster/docs/pushapk.rst" (17 Sep 2019, 2677 Bytes) of package /linux/www/firefox-69.0.1.source.tar.xz:
As a special service "Fossies" has tried to format the requested source page into HTML format (assuming markdown format).
Alternatively you can here view
the uninterpreted source code file.
A member file download can also be achieved by clicking within a package contents listing on the according byte size field. See also the last Fossies "Diffs"
side-by-side code changes report for "pushapk.rst": 68.0.2_vs_69.0
The push-apk task is in charge of uploading and publishing Android APKs onto Google Play store.
Push it all to Google Play
Before any request is made to Google Play, the push-apk task sanity checks the data passed over:
- APKs are signed with the correct certificates. This may not sound extremely important because Google Play is vigilant about APK signatures and will refuse any APK for which the signature is not valid. However, it is safer to bail out before any outbound traffic is done to Google Play. Besides, with this check, Google acts as a second factor instead of being the only actor accountable for signatures.
- All given APKs have matching data (version numbers, package names, etc.)
- No required processor architecture is missing, in order to upload them all in the same request. We have to publish them at the same time because some Android devices support several architectures. We have already had one big crash on these devices because an x86 APK was overseeded by its “brother in ARM”.
- APKs are multilocales
Then it uploads the APKs fetched in the previous task. Like said above, Google Play performs some additional checks on their end. For instance: * they ensure the APK buildIds (called "version code") are higher than the last ones they have on file. * they check whether the APKs are zipaligned (meaning, the APK archive has been optimized). Google Play errors are reported back.
These checks and actions are done in several components. Here's how they interact:
1. The “decision task” creates a task for pushapk_scriptworker 2/3. Scriptworker polls for pending tasks and check their scopes. 4. It downloads APKs via Chain of Trust. Scriptworker checks if the upstream tasks were altered. 5. Scriptworker defers valid tasks to pushapkscript. The latter validates APKs signatures, makes sure every APK architecture is present. 6. Pushapkscript calls MozApkPublisher with credentials and on-disk locations of APKs. 6/7. MozApkPublisher sanity checks the APKs. 8. MozApkPublisher opens the Google play credentials. 9. MozApkPublisher publishes APKs, listings and “what’s new”
For more information about the context, please see this blog post.