Lines Matching refs:provider
23 <a href="{@docRoot}guide/topics/providers/content-provider-basics.html"
39 highly secure content provider framework. For this reason, the sync adapter framework expects
40 that an app that uses the framework has already defined a content provider for its local data.
42 content provider, your sync adapter crashes.
46 strongly consider storing the local data in a content provider. Besides their importance for
49 provider, see <a href="{@docRoot}guide/topics/providers/content-provider-creating.html"
55 content provider, add a stub content provider to your app. A stub provider implements the
56 content provider class, but all of its required methods return {@code null} or {@code 0}. If you
57 add a stub provider, you can then use a sync adapter to transfer data from any storage
61 If you already have a content provider in your app, you don't need a stub content provider.
64 content provider, this lesson shows you how to add a stub content provider that allows you to
69 To create a stub content provider for your app, extend the class
71 snippet shows you how to create the stub provider:
81 * provider loaded correctly.
135 The sync adapter framework verifies that your app has a content provider by checking that your
136 app has declared a provider in its app manifest. To declare the stub provider in the
137 manifest, add a <code><a href="{@docRoot}guide/topics/manifest/provider-element.html"
138 ><provider></a></code> element with the following attributes:
142 <code>android:name="com.example.android.datasync.provider.StubProvider"</code>
145 Specifies the fully-qualified name of the class that implements the stub content provider.
148 <code>android:authorities="com.example.android.datasync.provider"</code>
151 A URI authority that identifies the stub content provider. Make this value your app's
152 package name with the string ".provider" appended to it. Even though you're declaring your
153 stub provider to the system, nothing tries to access the provider itself.
159 Determines whether other apps can access the content provider. For your stub content
160 provider, set the value to {@code false}, since there's no need to allow other apps to see
161 the provider. This value doesn't affect the interaction between the sync adapter framework
162 and the content provider.
168 Sets a flag that indicates that the provider is syncable. If you set this flag to
171 transfers with the content provider, but transfers only occur if you do them explicitly.
176 <code><a href="{@docRoot}guide/topics/manifest/provider-element.html"
177 ><provider></a></code> element to the app manifest:
190 <provider
191 android:name="com.example.android.datasync.provider.StubProvider"
192 android:authorities="com.example.android.datasync.provider"