Age | Commit message (Collapse) | Author |
|
|
|
If an ECM setting is restricted only by global device state, then it
should not be checked for a per-package restriction.
Fixes: 385317771
Test: atest EnhancedConfirmationInCallTest
Flag:
android.permission.flags.enhanced_confirmation_in_call_apis_enabled
Relnote: 25Q2 feature work
LOW_COVERAGE_REASON=b/387927331
Change-Id: Ia78acdca3071af6310d5bd5ce2c4db0c30195478
|
|
All new mainline APIs must be flagged.
Bug: 380052797
Test: atest PackageManagerShellCommandInstallTest
Flag: android.content.pm.sdk_dependency_installer
Relnote: N/A
Change-Id: I3b2677947608dbe772d81bc6875d45930095afa7
|
|
|
|
LOW_COVERAGE_REASON=NON_CODE_ONLY
Bug: 378965769
Flag: TEST_ONLY
Relnote: N/A
Change-Id: Ic09fa519fd43fc1790865b196ca612b4b4510846
|
|
This also adds a "reason" to the ecm dialog, to be used in determining
which version of the dialog to show
Bug: 364535720
Test: manual
Flag: android.permission.flags.enhanced_confirmation_in_call_apis_enabled
Relnote: 25Q2 feature work
Change-Id: I4be7e63d616d80ac196e88524b2f4cbda2d0c405
|
|
|
|
Bug: 380052797
Test: atest PackageManagerShellCommandInstallTest
Flag: NONE API to avoid hardcoding constant
Relnote: N/A
Change-Id: I8d32ce928ba83211bf864b088c205c56ef96289d
|
|
Followup fixes for RoleManager get/setDefaultHoldersForTest and is/setRoleVisibleForTest
LOW_COVERAGE_REASON=b/382484309
Relnote: N/A
Flag: com.android.permission.flags.cross_user_role_enabled
Bug: 381315745
Test: atest RoleManagerTest
Test: atest RoleManagerMultiUserTest
Change-Id: I19ddcd4a71682f89ccf32322833db3404f46c86f
|
|
This dialog looks similar to the existing ECM dialog, but has a
different message, about being blocked while in a phone call
Also removes the ecm "isUnknownCallOngoing", in favor of using
"isRestricted"
Test: atest EnhancedConfirmationInCallTest
Flag: android.permission.flags.unknown_call_package_install_blocking_enabled
Relnote: android 25Q2 feature
LOW_COVERAGE_REASON=FLAG_NOT_ENABLED
Change-Id: I113114c15df3df483e290f0bab00f5cecb2b44f8
|
|
|
|
Add role methods to assist in setting test role visiblity and default holders
LOW_COVERAGE_REASON=b/382484309
Relnote: N/A
Flag: com.android.permission.flags.cross_user_role_enabled
Bug: 381315745
Test: atest RoleManagerTest
Change-Id: I6d1d4200849a2be994f83da675fc57837ae7204f
|
|
This intent action will be used by settings to trigger the "action
blocked due to being in untrusted call" dialog
Bug: 364535720
Test: build
Flag: android.permission.flags.enhanced_confirmation_in_call_apis_enabled
Relnote: 25Q2 api
LOW_COVERAGE_REASON=NON_CODE_ONLY
Change-Id: Ic96ca1ce17ed5df3a4f4f736c6bd48ea599dadbe
|
|
|
|
Adds new APIs that let certain apps query if there is a call with an
unkown user (read: not a contact) ongoing. Also merges an InCallService
which tracks and updates this state
Bug: 364535720
Test: atest EnhancedConfirmationInCallTest
Flag: android.permission.flags.enhanced_confirmation_in_call_apis_enabled
Relnote: 25Q2 release
LOW_COVERAGE_REASON=FLAG_NOT_ENABLED
Change-Id: I2e260bd911a65f99dd7e7b7b4012b04ef7b51203
|
|
LOW_COVERAGE_REASON=FLAG_NOT_ENABLED
NO_IFTTT=brings jarjar inline with RoleParse transform
Relnote: N/A
Flag: com.android.permission.flags.cross_user_role_enabled
Test: atest RoleManagerTest
Test: atest RoleShellCommandTest
Bug: 372746716
Change-Id: I1b4da27df2f0d1862aa0031b2988bd7562f1a956
|
|
NO_IFTTT=Does not modify RoleParser logic
RelNote: N/A
Bug: 376728836
Flag: EXEMPT refactor
Test: build
Change-Id: I603adc9e8e584bbadda49903bca6c3aba30cad89
|
|
|
|
LOW_COVERAGE_REASON=NON_CODE_ONLY
Bug: 348197200
Test: atest android.compat.sjp.cts.StrictJavaPackagesTest#testApkInApex_nonClasspathClasses
Flag: NONE jarjar rule change
Change-Id: Ibb2b3551b42d97b4373012eb0a209fe3d5d2abff
|
|
Original change: https://android-review.googlesource.com/c/platform/packages/modules/Permission/+/3141526
Change-Id: I49938ff552f2af378d41a8c94f6e06aac4da9439
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Original change: https://android-review.googlesource.com/c/platform/packages/modules/Permission/+/3141526
Change-Id: I040015e09e5fa12c4ecb3420df2c88b3820fa925
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
The Lint FlaggedApi checks are currently configured as warnings. Add
existing violations to baselines files to prepare for turning the
FlaggedApi checks into errors.
Bug: 303434307
Test: treehugger
Flag: EXEMPT not possible to flag baseline changes
Change-Id: Iadacb5d31ec2f0975486a2bf14c971c3b17534ed
|
|
Bug: 347831320
Merged-In: I25f72c30c22429472bfc75073431f84431debd7b
Change-Id: I61898ec613c3103ae661acba81c9246cbacde8f8
|
|
The Lint FlaggedApi checks are currently configured as warnings. Add
existing violations to baselines files to prepare for turning the
FlaggedApi checks into errors.
Bug: 303434307
Test: treehugger
Flag: EXEMPT not possible to flag baseline changes
Merged-In: I990ce57cd5cdac44ee8b93565b45aa15790ad697
Change-Id: I990ce57cd5cdac44ee8b93565b45aa15790ad697
|
|
The Lint FlaggedApi checks are currently configured as warnings. Add
existing violations to baselines files to prepare for turning the
FlaggedApi checks into errors.
LOW_COVERAGE_REASON=NON_CODE_ONLY
Bug: 303434307
Test: treehugger
Flag: EXEMPT not possible to flag baseline changes
Change-Id: I990ce57cd5cdac44ee8b93565b45aa15790ad697
|
|
LOW_COVERAGE_REASON=NON_CODE_ONLY
Bug: 336313566
Test: All existing automation tests
Change-Id: If7d6e21eea10d7aa638a3965af84f25bc91f9e19
|
|
Test of *all* Mainline modules are currently configured in a single
`mainline-presubmit` Test Mapping group. This requires that users indicate the
module to install in every entry and is quite tedious.
The above approach also adds overhead due to installing, checking for, and
uninstalling Mainline modules between test module executions. This eats up
precious presubmit time and gets runtimes close to violating the SLO.
This change moves all PermissionController Mainline module tests into a
dedicated Test Mapping group that installs the Mainline module once before
executing all test modules. This also simplifies the configuration syntax by no
longer requiring brackets that indicate the, now implicit, Mainline module.
Bug: 328102821
Test: presubmit checks
Change-Id: Id7abaaa4096a4afe2175e79e629f59e84588dda4
|
|
Bug: 333395188
Test: build succeeds
LOW_COVERAGE_REASON=build change
Change-Id: Ieea1b2258072ac7b11c2f3d7c6b78ef924385fd5
|
|
|
|
Update the methods in IRoleController to catch the exception and
send it back to the caller's site.
This CL is a general fix for exception handling in IRoleController. It
also fixes and an issue we previously encountered where the role migration
failed when PC version mismatched. More details:
In the very rare cases that the PermissionController is not in an
updated version, it's possible that the system-server side of the role
migration code is in place but PC doesn't have the code to return the
legacyFallbackEnabledRoles. In this case currently we throw
UnsupportedOperationException. However, after this exception is thrown,
we didn't resolve the result for the cross-binder remote callback that's
being sent to PC. Hence in system-server it will wait until this call is
timedout.
Fixes: 325264710
Test: RoleManagerTest and additionally tested locally
LOW_COVERAGE_REASON=b/330904893
Change-Id: If77b32e39db5b0853cd54c8b74c871b0684611f5
|
|
The property is required to generate the "exportable" stubs (i.e. the
stubs that exclude DISABLED flagged apis or ENABLED + READ_WRITE flagged
apis), as the aconfig_declarations modules provide the information about
the state of the flags to metalava.
Test: m nothing
Bug: 329289292
Change-Id: I09e9db710d1b58460250f9f5cfd9f0891e39ebc6
|
|
This is required for ag/26422309
Bug: 327646201
Change-Id: I3fd69e865f5bb7c9b14adc8c20ab570d96fcb66f
|
|
We recently moved---well, copied---the "Restricted setting" dialog into
PermissionController. But, we're not using the new dialog yet.
The new dialog receives a different intent action than the old. So, to
migrate to the new dialog, we'll need to update all code that launches
the old intent. Fortunately, we've encapsulated this in
EnhancedConfirmationManager, so this is a one-line change.
Bug: 322026141
Test: CtsPermissionUiTestCases:android.permissionui.cts.EnhancedConfirmationManagerTest
Change-Id: Ied3e2712e409e056945be08e5911ae232149de68
|
|
|
|
In createRestrictedSettingDialogIntent, pass the provided
settingIdentifier to the dialog intent.
Fix: 323225971
Test: CtsPermissionUiTestCases:android.permissionui.cts.EnhancedConfirmationManagerTest
Change-Id: I59efd6601f4254c0fe74b8430ac1f3b6c6d91b6e
|
|
This API then enables TelephonyManager to expose the emergency
role holder to priviliged clients via getEmergencyAssistancePackageName.
Bug: 323157319
Test: atest RoleManagerTest
LOW_COVERAGE_REASON=Flagged test added but flag not enabled
Change-Id: I91089701248a32a720b488147405b2566cca2be9
|
|
Because Intent is more common, and we're not really getting major
advantages from how we're using a PendingIntent, return an Intent
instead of a PendingIntent.
Test: atest CtsPermissionUiTestCases:android.permissionui.cts.EnhancedConfirmationManagerTest
Fix: 324645464
Change-Id: I12062d20edb5a34950fd3cb9c9b993998b906041
|
|
ag/25918135 missed keeping some tests under the API check.
Also, correcting some documentation and using the codename until the
release when the correct sdk version would be available.
Bug: 286539356
Test: manual
Test: atest ParserConfigValidTest
Change-Id: I8a9175131eb364b9eee7947ca8be65882ad57db6
|
|
"sc_private_profile_api" into main
* changes:
Add the titleForPrivateProfile API
Generalise the code for various profile types - 6
Generalise the code for various profile types - 5
Generalise the code for various profile types - 4
Don't add primary profile in default group summary
Generalise the code for various profile types - 3
Generalise the code for various profile types - 2
Generalise the code for various profile types - 1
|
|
This API lets the safety sources set the title for the private
profile in the safety center config file.
This change also temporarily disables the linter. Safety Center team
will look into enabling it later.
Bug: 286539356
Test: manual
Change-Id: I99ab006240883065d290b2d9976f2a7c9bf7905e
|
|
In a recent commit, I introduced an AtomicInteger to generate unique
request codes that should never repeat.
But, I mistakenly made it a instance variable. Make it static so it
will be unique across instances of this class.
Bug: 26056958
Test: atest CtsPermissionUiTestCases:android.permissionui.cts.EnhancedConfirmationManagerTest
Change-Id: I04d0b7f2be854cf84155811b15282a66bbc92199
|
|
|
|
We're planning to move the "Restricted setting" dialog into
PermissionController. But, this dialog's intent action string,
Settings.ACTION_SHOW_RESTRICTED_SETTING_DIALOG, is currently bound to
the Settings app.
So, to ease the transition, this change defines a new intent action
string.
This string should only need to be accessed by PermissionController,
which handles the intent, and EnhancedConfirmationManager, which
constructs the intent.
Bug: 322026141
Test: manual
Change-Id: I1ba1d5bc778dd39239abb0dc6e0f0f32bea0c2b2
|
|
Use a unique requestCode for each call to PendingIntent.getActivity.
Without this, each call returns the same object, even if the supplied *extra*s differ. This is a problem because, it would mean that after the first call to PendingIntent.getActivity, each subsequent call will have the wrong extras.
Fix: 322891228
Test: manual
Change-Id: If774bfc1e03963ec32980ea7c935774eb930eaf0
|
|
Accept a 'settingIdentifier' argument to getRestrictedSettingDialogIntent.
We might want to use this to customize the dialog depending on the setting being requested. (Though, we're not doing that yet.)
Bug: 323225971
Change-Id: I51258724c48958176fa436b23f23cfa93a242dc3
Test: manual
|
|
|
|
This CL is created as a best effort to migrate test targets
to the new android ownership model. If you find incorrect or unnecessary
attribution in this CL, please create a separate CL to fix that.
For more details please refer to the link below,
<add g3 doc link>
Bug: 304529413
Test: N/A
(cherry picked from aosp/2939780)
Change-Id: Icbe839de65c4449f764bd579a9f8c43f9fac770d
|
|
|
|
We plan to call EnhancedConfirmationManager::setClearRestrictionAllowed
a hidden API method, from PermissionController. But,
PermissionController can't access hidden API methods. In order to make
this possible, setClearRestrictionAllowed will need to be upgraded from
hidden API to SystemApi.
The reason we need to call setClearRestrictionAllowed from
PermissionController is that we plan to move the
ActionDisabledByAppOpsDialog activity into PermissionController, and
modify it to call setClearRestrictionAllowed instead of directly setting
appops.
Bug: 322026141
Fix: 320517290
Test: atest CtsPermissionUiTestCases:android.permissionui.cts.EnhancedConfirmationManagerTest
Change-Id: Ibd068ac456846fd1af8e867a6b336853a7835c4a
|
|
|