Publication

From finished app to store: signing, version code and name, delivery format, listing, data declaration, test tracks, review, staged rollout and updates.

29 cards
6 topics
Free

Study this deck

The outline, topic by topic

Each topic is weighted the way the exam weighs it.

Concepts
Questions
Sort and link
The numbers
Scenarios
Understand

A few cards from the deck

Test track: what is it?
Show the answer
A store channel that delivers a build to a chosen audience before production: the team (internal), invited testers (closed) or any volunteer (open).
It lets you find flaws before the general public. You widen the audience as confidence rises: internal, then closed, then open, then production.
Which versionCode value will Google Play accept for the new build, given the last upload used versionCode 12?

```groovy
defaultConfig {
versionCode ???
versionName "1.4.1"
}
`
- 13
- 12
- 1.4.1
- "13", in quotes
Show the answer
13
The code must be an integer strictly greater than all those already used. 12 was used, 1.4.1 is not an integer, and the text "13" is not a number: only the version name is text.
In build.gradle, the … field is an integer that goes up with every upload, and … is the text shown to the user.
Show the answer
In build.gradle, the versionCode field is an integer that goes up with every upload, and versionName is the text shown to the user.
Example: versionCode 13 and versionName "1.4.0". You may keep the same name across two uploads, never the same code.
App signing: what is it?
Show the answer
The operation that stamps the package with a cryptographic fingerprint computed with a private key, to prove it really comes from its publisher.
Android refuses to install an update that is not signed with the same key as the installed app: losing the signing key means no longer being able to update.

Study this deck