From 85034c770ffeb78fc1137d27326822fe861f9a3e Mon Sep 17 00:00:00 2001 From: Songchun Fan Date: Tue, 28 Dec 2021 19:40:59 +0000 Subject: [PATCH] [SettingsProvider] fix server-side Readable maxTargetSdk check I must have used the wrong autocomplete from Intellij. Previous tests were not able to catch this because we have the same check on the client side. BUG: 172838801 BUG: 211711793 Test: atest android.appsecurity.cts.ReadableSettingsFieldsTest Change-Id: Ia3e4541564d9928ff04fa95564bb9e043d49e8ee --- .../src/com/android/providers/settings/SettingsProvider.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/SettingsProvider/src/com/android/providers/settings/SettingsProvider.java b/packages/SettingsProvider/src/com/android/providers/settings/SettingsProvider.java index 1e2d4e9ac93a6..927f11fd4f68e 100644 --- a/packages/SettingsProvider/src/com/android/providers/settings/SettingsProvider.java +++ b/packages/SettingsProvider/src/com/android/providers/settings/SettingsProvider.java @@ -2117,7 +2117,7 @@ public class SettingsProvider extends ContentProvider { } if ((ai.flags & ApplicationInfo.FLAG_TEST_ONLY) == 0) { // Skip checking readable annotations for test_only apps - checkReadableAnnotation(settingsType, settingName, ai.targetSandboxVersion); + checkReadableAnnotation(settingsType, settingName, ai.targetSdkVersion); } /** * some settings need additional permission check, this is to have a matching security