CtsShim.apk
versionCode='24' versionName='7.0-2996264'
CtsShimPriv.apk
versionCode='24' versionName='7.0-2996264'
Built here:
https://android-build.googleplex.com/builds/submitted/2996264/CtsShim/latest
This build is suitable for public release.
Bug: 29122339
Change-Id: I6533e3a3ed72de6d3887039e3e8cf527947c4166
* define a update hash such that com.android.cts.priv.ctsshim can't
be updated
* create a new APK to verify that <restrict-update> works as expected
Bug: 29311441
Change-Id: I61f3ae3dbd9c79b2dcdfbc30757af0f9a669fce6
This way the build server can build these apks, instead of the manual
process that was described in the README.
Bug: 29122339
Change-Id: I2d3d9924da908d501d3b1b07b4a317f8ad6f413f
The testing shim should be included as a prebuilt. This allows
us to destroy the signing key. This means that the shim can never
be upgraded in the field; aside from its intended purpose in
a CTS test.
Bug: 28398205
Change-Id: I033835d227416ff8aa6602abfc8b977c74cb666d
There are now three rules that guard intent filter priorities:
1) Only privileged applications will be granted a >0 priority
filter [previously, _all_ system applications could do this]
2) There are certain actions that are considered protected [eg
ACTION_VIEW, ACTION_SEND, ...] and even privileged applications
will NOT be granted a >0 priority filter. There is one, and
only one, exception for the SetupWizard.
3) Updates will NOT be granted a priority greater than the priority
defined on the system image.
Bug: 27450489
Change-Id: Ifcec4d7a59e684331399abc41eea1bd6876155a4
