From c236335ea44230380272407b47d4a6d83ac349ed Mon Sep 17 00:00:00 2001 From: matchboxbananasynergy <107055883+matchboxbananasynergy@users.noreply.github.com> Date: Mon, 15 Jan 2024 23:28:21 +0000 Subject: [PATCH] Add Contact Scopes section to Usage guide --- static/usage.html | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) diff --git a/static/usage.html b/static/usage.html index 3529fa8a..1c8bd7c3 100644 --- a/static/usage.html +++ b/static/usage.html @@ -55,6 +55,7 @@
For an introduction, read + https://developer.android.com/guide/topics/providers/contacts-provider.
+ +The Contact Scopes feature enables the user to grant an app read access to a + subset of data in the OS ContactsProvider. Granting write access (insert(), + update(), delete()) is not supported.
+ +Read access can be granted to the following scopes:
+ +Type and name of account that contact is stored in is fully hidden from the + app. Name of contact account is usually the same as email address of that + account.
+ +Access to SIM phonebook data is fully stubbed out: an empty and immutable + content provider is exposed instead of the actual SIM phonebook. Implementations + of legacy (ICC) and modern SIM stub phonebook providers are added to + packages/services/Telephony.
+ +The Contact Scopes feature is enabled per-app. When it's enabled, app's calls + to contacts provider and to SIM phonebook providers are redirected, respectively, + to ScopedContactsProvider and to stub SIM phonebook providers.
+