A provider can specify some permissions. Other applications must apply for permissions to access the data of the provider. These permissions ensure that the user understands what data the application will attempt to access. Based on the requirements of the provider, other applications need to apply for the required permissions to access the provider. When the application is installed, you can see the school-wide nature of the application.
If the provider application does not specify any permissions, other applications cannot access the data of the provider. However, components in the provider's application always have full read and write permissions, regardless of whether or not permissions are specified.
As explained above, in order to obtain data from the user dictionary, This provider requires the permission to apply for Android. Permission. read_user_dictionary. To insert, update, or delete data, the provider also has an independent Android. Permission. write_user_dictionary permission.
To obtain the permissions required to access a provider, the application must apply in the <uses-Permission> element of its configuration file. When the android Package Manager installs this application, the user must approve all permissions applied for by the application. If the user approves these permissions, the Package Manager will continue the installation. If the user does not approve these permissions, the Package Manager will ignore this installation.
The following <uses-permissiion> element applies for the read permission on the user dictionary provisioner:
<Uses-Permission Android: Name = "android. Permission. read_user_dictionary">
The impact of the Providers' access permissions will be explained in more detail in the "Security and permissions" guide.