I know this has been discussed yet I wanted to ask about the current state of the matter. Do i have to create a ContentProvider to use CursorLoader in connection with a sqlite database? 

I found

[https://stackoverflow.com/questions/7182485/usage-cursorloader-without-contentprovider/7422343#7422343][1]

Looks exactly what I was hoping for yet as Emmby commented

 -  Users should be aware of one limitation, which is that it has no mechanism to refresh on data changes (as Loaders are supposed to do)

So another solution is mentioned 

[https://github.com/commonsguy/cwac-loaderex][2]

yet again some drawback is pointed out

 - However, to make use of the automatic re-querying, you need to use the same loader for the UI as well as for the updates, limiting its usability for background services.

Of course when using LoaderManager we want to get all the benefits for which it was introduced. So my question is if there is a way to use LoaderManager in connection with a sqlite database without having to implement a content provider yet have all the benefits of it.

Thanks


  [1]: https://stackoverflow.com/questions/7182485/usage-cursorloader-without-contentprovider/7422343#7422343
  [2]: https://github.com/commonsguy/cwac-loaderex

android - CursorLoader &amp; SQLite without Content Provider

I try to understand the Android synchronization logic. What I don&#39;t understand is the file `syncadapter.xml` contained in the Android SDK sample project `SampleSyncAdapter`. If you downloaded the SDK samples it should be in the following folder:

    SDK/android-sdk-PLATFORM/samples/android-VERSION/SampleSyncAdapter/res/xml/syncadapter.xml

I read, the authority of a content provider should be a string or a reference to a resource. What exactly is the content authority and where is `com.android.contacts`? Here is the content of the file (w/o license information and comments, API level 16).

    &lt;sync-adapter xmlns:android=&quot;http://schemas.android.com/apk/res/android&quot;
        android:contentAuthority=&quot;com.android.contacts&quot;
        android:accountType=&quot;com.example.android.samplesync&quot;
        android:supportsUploading=&quot;false&quot;
        android:userVisible=&quot;true&quot;
    /&gt;

How do I use the Android SyncAdapter?

What is the difference between **ContentProviders** and **ContentResolver**? I do not want for the `SQLite` database. I am developing an application for media. 

What is difference between contentprovider and contentResolver in android

## Background

I maintain a [library](https://github.com/stkent/bugshaker-android) whose core functionality involves sharing programmatically-captured screenshots to external email applications.

I use a `FileProvider` to accomplish this, which means my library&#39;s manifest contains [a `&lt;provider&gt;` tag](https://github.com/stkent/bugshaker-android/blob/df05e919882713c93a44af61f947fb7ac3e99fbc/bugshaker/src/main/AndroidManifest.xml):

&lt;!-- language: xml --&gt;

    &lt;provider
        android:name=&quot;android.support.v4.content.FileProvider&quot;
        android:authorities=&quot;${applicationId}.bugshaker.fileprovider&quot;
        android:exported=&quot;false&quot;
        android:grantUriPermissions=&quot;true&quot;&gt;
        &lt;meta-data
            android:name=&quot;android.support.FILE_PROVIDER_PATHS&quot;
            android:resource=&quot;@xml/filepaths&quot; /&gt;
    &lt;/provider&gt;

`filepaths.xml` is defined as follows:

&lt;!-- language: xml --&gt;

    &lt;paths&gt;
        &lt;files-path path=&quot;bug-reports/&quot; name=&quot;bug-reports&quot; /&gt;
    &lt;/paths&gt;

A consumer of my library has an application which itself uses a `FileProvider` to share files. My expectation was that it should be possible to allow both providers to share files if the consuming application used the following manifest `&lt;provider&gt;` tag:

&lt;!-- language: xml --&gt;

    &lt;provider
        android:authorities=&quot;${applicationId}.fileprovider;${applicationId}.bugshaker.fileprovider&quot;
        android:exported=&quot;false&quot;
        android:grantUriPermissions=&quot;true&quot;
        android:name=&quot;android.support.v4.content.FileProvider&quot;
        tools:replace=&quot;android:authorities&quot;&gt;
        &lt;meta-data
            android:name=&quot;android.support.FILE_PROVIDER_PATHS&quot;
            android:resource=&quot;@xml/file_paths&quot;
            tools:replace=&quot;android:resource&quot; /&gt;
    &lt;/provider&gt;

This manifest entry:

- specifies two `Provider` authorities, `${applicationId}.fileprovider` (for application file sharing) and `${applicationId}.bugshaker.fileprovider` (for library file sharing);
- references an updated `filepaths.xml`, which contains separate directory definitions for application-generated files and library-generated files:

&lt;!-- language: xml --&gt;

    &lt;paths&gt;
        &lt;external-path
            name=&quot;redacted&quot;
            path=&quot;&quot; /&gt;
        &lt;files-path
            name=&quot;bug-reports&quot;
            path=&quot;bug-reports/&quot; /&gt;
    &lt;/paths&gt;

After building the application, we have confirmed that the generated manifest has had the correct nodes replaced with these updated values.

However, when the application using this configuration is assembled (successfully) and run, we see a crash on launch:

&lt;!-- language: lang-none --&gt;

    E: FATAL EXCEPTION: main
       Process: com.stkent.bugshakertest, PID: 11636
       java.lang.RuntimeException: Unable to get provider android.support.v4.content.FileProvider: java.lang.NullPointerException: Attempt to invoke virtual method &#39;android.content.res.XmlResourceParser android.content.pm.PackageItemInfo.loadXmlMetaData(android.content.pm.PackageManager, java.lang.String)&#39; on a null object reference
           at android.app.ActivityThread.installProvider(ActivityThread.java:5856)
           at android.app.ActivityThread.installContentProviders(ActivityThread.java:5445)
           at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5384)
           at android.app.ActivityThread.-wrap2(ActivityThread.java)
           at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1545)
           at android.os.Handler.dispatchMessage(Handler.java:102)
           at android.os.Looper.loop(Looper.java:154)
           at android.app.ActivityThread.main(ActivityThread.java:6119)
           at java.lang.reflect.Method.invoke(Native Method)
           at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
           at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
        Caused by: java.lang.NullPointerException: Attempt to invoke virtual method &#39;android.content.res.XmlResourceParser android.content.pm.PackageItemInfo.loadXmlMetaData(android.content.pm.PackageManager, java.lang.String)&#39; on a null object reference
           at android.support.v4.content.FileProvider.parsePathStrategy(FileProvider.java:583)
           at android.support.v4.content.FileProvider.getPathStrategy(FileProvider.java:557)
           at android.support.v4.content.FileProvider.attachInfo(FileProvider.java:375)
           at android.app.ActivityThread.installProvider(ActivityThread.java:5853)
           at android.app.ActivityThread.installContentProviders(ActivityThread.java:5445)&#160;
           at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5384)&#160;
           at android.app.ActivityThread.-wrap2(ActivityThread.java)&#160;
           at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1545)&#160;
           at android.os.Handler.dispatchMessage(Handler.java:102)&#160;
           at android.os.Looper.loop(Looper.java:154)&#160;
           at android.app.ActivityThread.main(ActivityThread.java:6119)&#160;
           at java.lang.reflect.Method.invoke(Native Method)&#160;
           at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)&#160;
           at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)&#160;

Using the debugger, I am able to see that the method `FileProvider.parsePathStrategy` invokes [`PackageManager.resolveContentProvider`](https://developer.android.com/reference/android/content/pm/PackageManager.html#resolveContentProvider(java.lang.String,%20int)) with the authority string `&quot;${applicationId}.fileprovider;${applicationId}.bugshaker.fileprovider&quot;`. `resolveContentProvider` then returns null, leading to this NPE.

If I manually call `resolveContentProvider` while paused at this instruction and pass either `&quot;${applicationId}.fileprovider&quot;` _or_ `&quot;${applicationId}.bugshaker.fileprovider&quot;`, `resolveContentProvider` instead returns a non-null `ProviderInfo` instance (which would seem to be the expected result).

This difference confuses me because the [`&lt;provider&gt;` element documentation](https://developer.android.com/guide/topics/manifest/provider-element.html) states that multiple authorities are supported:

&gt; A list of one or more URI authorities that identify data offered by the content provider. Multiple authorities are listed by separating their names with a semicolon. To avoid conflicts, authority names should use a Java-style naming convention (such as com.example.provider.cartoonprovider). Typically, it&#39;s the name of the ContentProvider subclass that implements the provider
&gt; 
&gt; There is no default. At least one authority must be specified.

## Questions

- Is it possible to have a single application expose a `FileProvider` with multiple authorities and file paths?
    - If so, what do I need to change to make that work?
    - If not, are there other ways to configure file sharing within my library that avoid conflicts such as this one?


Possible to use multiple authorities with FileProvider?

I am experimenting with the NotesList sample program in the Android SDK. I&#39;ve made a slight variation in the program, but when I install my edited version I keep getting the message INSTALL_FAILED_CONFLICTING_PROVIDER in the console when I try to install it when the original notes program is already on the device. What do I need to change in the Provider to make it a unique database? It works fine if I uninstall the original notes program and then install my edited version. 

Install shows error in console: INSTALL FAILED CONFLICTING PROVIDER

I&#39;m looking for a way to correctly share (not OPEN) an internal file with external application using Android Support library&#39;s [FileProvider][1]. 

Following the example on the docs,

    &lt;provider
        android:name=&quot;android.support.v4.content.FileProvider&quot;
        android:authorities=&quot;com.example.android.supportv4.my_files&quot;
        android:grantUriPermissions=&quot;true&quot;
        android:exported=&quot;false&quot;&gt;
        &lt;meta-data
            android:name=&quot;android.support.FILE_PROVIDER_PATHS&quot;
            android:resource=&quot;@xml/my_paths&quot; /&gt;
    &lt;/provider&gt;

and using ShareCompat to share a file to other apps as follows:
    
    ShareCompat.IntentBuilder.from(activity)
    .setStream(uri) // uri from FileProvider
    .setType(&quot;text/html&quot;)
    .getIntent()
    .addFlags(Intent.FLAG_GRANT_READ_URI_PERMISSION)

does not work, since the FLAG_GRANT_READ_URI_PERMISSION only grants permission for the Uri specified on the `data` of the intent, not the value of the `EXTRA_STREAM` extra (as was set by `setStream`).

I tried to compromise security by setting `android:exported` to `true` for the provider, but `FileProvider` internally checks if itself is exported, when so, it throws an exception.

  [1]: http://developer.android.com/reference/android/support/v4/content/FileProvider.html

How to use support FileProvider for sharing content to other apps?

I have set up Gradle to add package name suffix to my debug app so I could have release version that I&#39;m using and debug version on one phone. I was referencing this: http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Build-Types

My build.gradle file looks like this:

    ...
    android
    {
        ...
        buildTypes
        {
            debug
            {
                packageNameSuffix &quot;.debug&quot;
                versionNameSuffix &quot; debug&quot;
            }
        }
    }

Everything works fine until I start using a ContentProvider in my app. I get: 

    Failure [INSTALL_FAILED_CONFLICTING_PROVIDER]

I understand that this happens because two apps (release and debug) are registering same ContentProvider authority.

I see one possibility to solve this. If I understand correctly, you should be able to specify different files to use when building. Then I should be able to put different authorities in different resource files (and from Manifest set authority as string resource) and tell Gradle to use different resource for debug build. Is that possible? If yes then any hints on how to achieve that would be awesome!

Or maybe it&#39;s possible to directly modify Manifest using Gradle? Any other solution on how to run same app with ContentProvider on one device is always welcome.

Using build types in Gradle to run same app that uses ContentProvider on one device

I am trying to implement the Content-Provider-Sync Adapter pattern as discussed at [Google IO](http://dl.google.com/googleio/2010/android-developing-RESTful-android-apps.pdf) - slide 26. My content provider is working, and my sync works when I trigger it from the Dev Tools Sync Tester application, however when I call ContentResolver.requestSync(account, authority, bundle) from my ContentProvider, my sync is never triggered.

    ContentResolver.requestSync(
    		account, 
    		AUTHORITY, 
    		new Bundle());

Edit -- added manifest snippet
My manifest xml contains:

    &lt;service
        android:name=&quot;.sync.SyncService&quot;
        android:exported=&quot;true&quot;&gt;
        &lt;intent-filter&gt;
            &lt;action
                android:name=&quot;android.content.SyncAdapter&quot; /&gt;
        &lt;/intent-filter&gt;
        &lt;meta-data android:name=&quot;android.content.SyncAdapter&quot;
		android:resource=&quot;@xml/syncadapter&quot; /&gt;
    &lt;/service&gt;
--Edit

My syncadapter.xml associated with my sync service contains:  

    &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
    &lt;sync-adapter xmlns:android=&quot;http://schemas.android.com/apk/res/android&quot;  
        android:contentAuthority=&quot;AUTHORITY&quot;
        android:accountType=&quot;myaccounttype&quot;
        android:supportsUploading=&quot;true&quot;
    /&gt;

Not sure what other code would be useful.  The account passed to requestSync is of &quot;myaccounttype&quot; and the AUTHORITY passed to the call matches my syc adapter xml.

Is ContentResolver.requestSync the correct way to request a sync?  It looks like the sync tester tool binds directly to the service and calls start sync, but that seems like it defeats the purpose of integrating with the sync architecture.

If that is the correct way to request a sync then why would the sync tester work, but not my call to ContentResolver.requestSync?  Is there something I need to pass in the bundle?

I am testing in the emulator on devices running 2.1 and 2.2.

Why does ContentResolver.requestSync not trigger a sync?

I understand that Content Providers are made to allow publicly sharing data between applications. However, I&#39;m wondering if anyone has thoughts about making a Content Provider to use just within your own app. Would there be any advantages to doing this? Any disadvantages? 

In the past I&#39;ve just implemented the SQliteOpenHelper to access data from my database, but I&#39;m considering creating a Content Provider. I feel like the URI approach to requesting data is clear and concise. On the other hand, will using a Content Provider just for my application be redundant ( since within it I will have a SQliteOpenHelper class ) and more work than I need?

When to use a Content Provider

Android SDK documentation says that `startManagingCursor()` method is depracated:

&gt; This method is deprecated. Use the new CursorLoader class with LoaderManager instead; this is also available on older platforms through the Android compatibility package. This method allows the activity to take care of managing the given Cursor&#39;s lifecycle for you based on the activity&#39;s lifecycle. That is, when the activity is stopped it will automatically call deactivate() on the given Cursor, and when it is later restarted it will call requery() for you. When the activity is destroyed, all managed Cursors will be closed automatically. If you are targeting HONEYCOMB or later, consider instead using LoaderManager instead, available via getLoaderManager()

So I would like to use `CursorLoader`. But how can I use it with custom `CursorAdapter` and without `ContentProvider`, when I needs URI in constructor of `CursorLoader`?

CursorLoader usage without ContentProvider

I&#39;m building an app where I have a table for events and a table for venues. I want to be able to grant other applications access to this data. I have a few questions related to best practices for this kind of problem.

1. **How should I structure the database classes?**
I currently have classes for EventsDbAdapter and VenuesDbAdapter, which provide the logic for querying each table, while having a separate DbManager (extends SQLiteOpenHelper) for managing database versions, creating/upgrading databases, giving access to database (getWriteable/ReadeableDatabase). Is this the recommended solution, or would I be better off either consolidating everything to one class (ie. the DbManager) or separation everything and letting each Adapter extends SQLiteOpenHelper?

2. **How should I design content providers for multiple tables?**
Extending the previous question, should I use one Content Provider for the whole app, or should I create separate providers for Events and Venues?

Most examples I find only deal with single table apps, so I would appreciate any pointers here.

Best practices for exposing multiple tables using content providers in Android

i have done SQLite database programming for Android, but i dont know anything about
Content-Provider except this: &quot;As i have referred &lt;a href=&quot;http://developer.android.com/guide/topics/providers/content-providers.html&quot;&gt;Android Developer page &lt;/a&gt;, Android SDK explained about &quot;Content-provider&quot; as it is used to store and retrieve data.&quot; 

But then, 

1. What is the exact difference between &quot;Content-Provider&quot; and &quot;SQLite Database&quot;?
2. Which is best to store data, when ?

Any example or helps !!
 



Exact Difference between &quot;Content-Provider&quot; and &quot;SQLite Database&quot;

This week I&#39;ve been learning all about ContentProvider and using the SQLiteOpenHelper class to manage the creation and upgrading of the database inside of a provider.  Specifically, I&#39;ve been reading through the NotePad example from the sdk&#39;s samples directory.  

Now, I can see that SQLiteOpenHelper has a close() method.  I&#39;m aware that leaving idle databases open is bad practice and can cause memory leaks and whatnot (unless [this][1] discussion is headed in the right direction).  If I were using the class in an Activity, then I would simply call close() in the onDestroy() method, but as far as I know, ContentProvider does not have the same life cycle that activities do.  The code for NotePad never seems to call close(), so I would like to assume that it is handled by SQLiteOpenHelper or some other piece of the puzzle, but I&#39;d really like to know for sure.  I don&#39;t really trust the sample code that much, either...

Question summary:  When should we close the database in a provider, if at all?


  [1]: https://stackoverflow.com/questions/1379200/android-content-provider-database-leak-issue


Closing the database in a ContentProvider

when I try to attach a file to an email, I get a java.io.FileNotFoundException: No content provider logcat output. 
If anyone could tell me what I am doing wrong or what I should do instead, that would be great.Thank you.

This is how I add the files to the email..:

    Intent sendIntent = new Intent(Intent.ACTION_SEND);
    		        sendIntent.putExtra(Intent.EXTRA_STREAM, uri);
    		        sendIntent.setType(&quot;video/3gp&quot;);
    		        sendIntent.setType(&quot;video/mp4&quot;);
    		        startActivity(sendIntent);

...and here is the entire logcat error output:

    07-20 09:15:58.364: ERROR/Mms/media(168): IOException caught while opening or reading stream
    07-20 09:15:58.364: ERROR/Mms/media(168): java.io.FileNotFoundException: No content provider: /sdcard/Video0006.mp4
    07-20 09:15:58.364: ERROR/Mms/media(168):     at android.content.ContentResolver.openAssetFileDescriptor(ContentResolver.java:507)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at android.content.ContentResolver.openInputStream(ContentResolver.java:345)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at com.android.mms.model.MediaModel.initMediaSize(MediaModel.java:268)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at com.android.mms.model.MediaModel.&lt;init&gt;(MediaModel.java:76)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at com.android.mms.model.RegionMediaModel.&lt;init&gt;(RegionMediaModel.java:40)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at com.android.mms.model.VideoModel.&lt;init&gt;(VideoModel.java:55)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at com.android.mms.model.VideoModel.&lt;init&gt;(VideoModel.java:48)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at com.android.mms.data.WorkingMessage.changeMedia(WorkingMessage.java:434)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at com.android.mms.data.WorkingMessage.setAttachment(WorkingMessage.java:343)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at com.android.mms.ui.ComposeMessageActivity.addVideo(ComposeMessageActivity.java:2472)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at com.android.mms.ui.ComposeMessageActivity.addAttachment(ComposeMessageActivity.java:2544)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at com.android.mms.ui.ComposeMessageActivity.handleSendIntent(ComposeMessageActivity.java:2521)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at com.android.mms.ui.ComposeMessageActivity.initialize(ComposeMessageActivity.java:1703)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at com.android.mms.ui.ComposeMessageActivity.onCreate(ComposeMessageActivity.java:1633)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2459)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2512)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at android.app.ActivityThread.access$2200(ActivityThread.java:119)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1863)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at android.os.Handler.dispatchMessage(Handler.java:99)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at android.os.Looper.loop(Looper.java:123)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at android.app.ActivityThread.main(ActivityThread.java:4363)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at java.lang.reflect.Method.invokeNative(Native Method)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at java.lang.reflect.Method.invoke(Method.java:521)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
    07-20 09:15:58.364: ERROR/Mms/media(168):     at dalvik.system.NativeStart.main(Native Method)



What to do when - java.io.FileNotFoundException: No content provider?

Does anybody know what this means?

    12-31 20:55:45.861: ERROR/AndroidRuntime(12478): Caused by: java.lang.IllegalArgumentException: the bind value at index 1 is null
    12-31 20:55:45.861: ERROR/AndroidRuntime(12478):     at android.database.sqlite.SQLiteProgram.bindString(SQLiteProgram.java:234)
    12-31 20:55:45.861: ERROR/AndroidRuntime(12478):     at android.database.sqlite.SQLiteQuery.bindString(SQLiteQuery.java:182)
    12-31 20:55:45.861: ERROR/AndroidRuntime(12478):     at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:48)
    12-31 20:55:45.861: ERROR/AndroidRuntime(12478):     at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1345)
    12-31 20:55:45.861: ERROR/AndroidRuntime(12478):     at android.database.sqlite.SQLiteQueryBuilder.query(SQLiteQueryBuilder.java:330)
    12-31 20:55:45.861: ERROR/AndroidRuntime(12478):     at android.database.sqlite.SQLiteQueryBuilder.query(SQLiteQueryBuilder.java:280)
    12-31 20:55:45.861: ERROR/AndroidRuntime(12478):     at net.lp.collectionista.providers.ProductContentProvider.query(ProductContentProvider.java:350)
    12-31 20:55:45.861: ERROR/AndroidRuntime(12478):     at android.content.ContentProvider$Transport.query(ContentProvider.java:163)
    12-31 20:55:45.861: ERROR/AndroidRuntime(12478):     at android.content.ContentResolver.query(ContentResolver.java:245)
    12-31 20:55:45.861: ERROR/AndroidRuntime(12478):     at net.lp.collectionista.providers.FacadeContentProvider.query(FacadeContentProvider.java:563)
    12-31 20:55:45.861: ERROR/AndroidRuntime(12478):     at android.content.ContentProvider$Transport.query(ContentProvider.java:163)
    12-31 20:55:45.861: ERROR/AndroidRuntime(12478):     at android.content.ContentResolver.query(ContentResolver.java:245)
    12-31 20:55:45.861: ERROR/AndroidRuntime(12478):     at net.lp.collectionista.util.ScanAddTask.existsProduct(ScanAddTask.java:164)
    12-31 20:55:45.861: ERROR/AndroidRuntime(12478):     at net.lp.collectionista.util.ScanAddTask.&lt;init&gt;(ScanAddTask.java:71)
    12-31 20:55:45.861: ERROR/AndroidRuntime(12478):     at net.lp.collectionista.util.ItemScanAddTask.&lt;init&gt;(ItemScanAddTask.java:34)
    12-31 20:55:45.861: ERROR/AndroidRuntime(12478):     at net.lp.collectionista.ui.activities.collections.cd.CDCollectionViewWindow$MusicCDItemScanAddTask.&lt;init&gt;(CDCollectionViewWindow.java:147)
    12-31 20:55:45.861: ERROR/AndroidRuntime(12478):     at net.lp.collectionista.ui.activities.collections.cd.CDCollectionViewWindow.restoreLocalState(CDCollectionViewWindow.java:1044)
    12-31 20:55:45.861: ERROR/AndroidRuntime(12478):     at net.lp.collectionista.ui.activities.collections.cd.CDCollectionViewWindow.onRestoreInstanceState(CDCollectionViewWindow.java:966)
    12-31 20:55:45.861: ERROR/AndroidRuntime(12478):     at android.app.Activity.performRestoreInstanceState(Activity.java:815)
    12-31 20:55:45.861: ERROR/AndroidRuntime(12478):     at android.app.Instrumentation.callActivityOnRestoreInstanceState(Instrumentation.java:1096)
    12-31 20:55:45.861: ERROR/AndroidRuntime(12478):     at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2641)



IllegalArgumentException: the bind value at index 1 is null

Last Couple of days I have been  spending times on learning new **Android Architecture Components** . After following up some blog posts, documentation &amp; tutorials , every components were getting clear to me . But Suddenly I realised what about our old friend **Content Provider** . I might sound silly , because before writing this question I have spent quite a time searching , Am I be the only one came up with this question . I hadn&#39;t got any helpful solution . Anyways here is it , if I want to build up an app with local DB , I will now obviously choose new Architecture Components (live data , view model , room ) without any farther thinking this will be very helpful to make app 10x robust . But If I want my DB datas accessible to other app , for instance To Widget How do I integrate Content Provider with Room ?

  

Room persistence library and Content provider

I am creating an application in which I want to capture a image and then I want to send that image in the email as a attachment.

I am opening a camera using `android.provider.MediaStore.ACTION_IMAGE_CAPTURE` intent action and I am passing the Uri of the file as a parameter `EXTRA_OUTPUT` to get the image back to the file. This is working perfectly and I am able to get the captured image if I use the `external storage uri` as a  `EXTRA_OUTPUT` but if I use the data folder uri it is not working and the camera is not closing and its all buttons are not working.

Here is my code for get the result in the external storage directory 

    Intent i = new Intent(android.provider.MediaStore.ACTION_IMAGE_CAPTURE);
    File out = Environment.getExternalStorageDirectory();
    out = new File(out, imagename);
    i.putExtra(MediaStore.EXTRA_OUTPUT, Uri.fromFile(out));
    startActivityForResult(i, CAMERA_RESULT);

And this code is for get the image in the data folder

    Intent i = new Intent(android.provider.MediaStore.ACTION_IMAGE_CAPTURE);
    File out = getFilesDir();
    out = new File(out, MyPharmacyOptions.PRESCRIPTION_IMAGE_NAME);
    i.putExtra(MediaStore.EXTRA_OUTPUT, Uri.fromFile(out));
    startActivityForResult(i, CAMERA_RESULT);

I knew that the **data folder is not accessible to third application** so may be this causes an issue so I have create one content provider to share the file.

Here is my content provide class

    public class MyContentProvider extends ContentProvider {
    	private static final String Tag = RingtonContentProvider.class.getName();
    	public static final Uri CONTENT_URI = Uri
    			.parse(&quot;content://x.y.z/&quot;);
    	private static final HashMap&lt;String, String&gt; MIME_TYPES = new HashMap&lt;String, String&gt;();
    
    	static {
    		MIME_TYPES.put(&quot;.mp3&quot;, &quot;audio/mp3&quot;);
    		MIME_TYPES.put(&quot;.wav&quot;, &quot;audio/mp3&quot;);
    		MIME_TYPES.put(&quot;.jpg&quot;, &quot;image/jpeg&quot;);
    	}
    
    	@Override
    	public boolean onCreate() {
    		return true;
    	}
    
    	@Override
    	public String getType(Uri uri) {
    		String path = uri.toString();
    
    		for (String extension : MIME_TYPES.keySet()) {
    			if (path.endsWith(extension)) {
    				return (MIME_TYPES.get(extension));
    			}
    		}
    
    		return (null);
    	}
    
    	@Override
    	public ParcelFileDescriptor openFile(Uri uri, String mode)
    			throws FileNotFoundException {
    		File f = new File(getContext().getFilesDir(), uri.getPath());
    
    		if (f.exists()) {
    			return (ParcelFileDescriptor.open(f, ParcelFileDescriptor.MODE_READ_ONLY));
    		}
    
    		throw new FileNotFoundException(uri.getPath());
    	}
    
    	@Override
    	public Cursor query(Uri url, String[] projection, String selection,
    			String[] selectionArgs, String sort) {
    		throw new RuntimeException(&quot;Operation not supported&quot;);
    	}
    
    	@Override
    	public Uri insert(Uri uri, ContentValues initialValues) {
    		File file = new File(getContext().getFilesDir(), uri.getPath());
    		if(file.exists()) file.delete();
    		try {
    			file.createNewFile();
    		} catch (IOException e) {
    			// TODO Auto-generated catch block
    			e.printStackTrace();
    		}
    		
    		return Uri.fromFile(file);
    	}
    
    	@Override
    	public int update(Uri uri, ContentValues values, String where,
    			String[] whereArgs) {
    		throw new RuntimeException(&quot;Operation not supported&quot;);
    	}
    
    	@Override
    	public int delete(Uri uri, String where, String[] whereArgs) {
    		File f = new File(getContext().getFilesDir(), &quot;image1.jpg&quot;);
    		if(f.exists()) f.delete();
    		f = new File(getContext().getFilesDir(), &quot;image2.jpg&quot;);
    		if(f.exists()) f.delete();
    		
    		getContext().getContentResolver().notifyChange(CONTENT_URI, null);
    		
    	}
    }

So to use this content provide I am using following code to pass the uri to the camera activity

    Intent i = new Intent(android.provider.MediaStore.ACTION_IMAGE_CAPTURE);
    Uri uri = MyContentProvider.CONTENT_URI;
    uri = Uri.withAppendedPath(uri, imagename);
    getContentResolver().insert(uri, null);
    getContentResolver().notifyChange(RingtonContentProvider.CONTENT_URI, null);
    Log.d(Tag, uri.toString());
    i.putExtra(MediaStore.EXTRA_OUTPUT, uri);
    
    startActivityForResult(i, CAMERA_RESULT);

Now if I pass the url other then external storage directory the camera is opening but it is not closing in emulator but in device the camera is going to closed but I am not getting the result.

I have declared this content provide in the manifest file 

    &lt;provider
    android:name=&quot;.contentproviders.MyContentProvider&quot;
    android:authorities=&quot;x.y.z&quot; /&gt;

Also I have given the permission to **write the external storage** and also for **use the camera**.

I am able to capture the image using the external storage but I want to store the image in the data directory instead of external storage because if the external storage in not available I want to capture the image and want to send mail.

If I create content provide then I can also share my image to the email application.

**If we not provide the extras with the camera intent it will return the image as a byte[] in the activity result as a data extra but this is for the purpose of the thumbnail so I can&#39;t get the high resolution image using this way.**
 

How to get camera result as a uri in data folder?

The [documentation on Android content providers](http://developer.android.com/guide/topics/providers/content-providers.html) describes using a `ContentResolver`, obtained from `getContentResolver()`, to access the content.

However there is also a `ContentProviderClient`, which can be obtained from `getContentResolver().acquireContentProviderClient(authority)`.  It seems to provide more or less the same methods available in the `ContentResolver` for accessing content from the provider.

When should I use a `ContentProviderClient` instead of just using the `ContentResolver` directly?  What are the benefits?

using ContentProviderClient vs ContentResolver to access content provider

I am trying to get an image from the gallery app from one of the folders from the Google+ synced photos. After selecting the image, the Uri is being passed back correctly. But when I try to get the actual path of that image on the storage device, so that I can use it, it crashes. The problem seems to be specifically with the **picasa content provider**.

Tested on Nexus S and Nexus 7, and other devices as well.

&lt;pre&gt;
E/AndroidRuntime(14572): java.lang.RuntimeException: Failure delivering result ResultInfo{who=null, request=1, result=-1, data=Intent { dat=content://com.google.android.gallery3d.provider/picasa/item/5427003652908228690 }}
&lt;/pre&gt;

Here, the dat field seems to be correctly passing the Uri, but when I try to fetch the image&#39;s location, it crashes with the following error.

&lt;pre&gt;
W/GalleryProvider(14381): unsupported column: _data
&lt;/pre&gt;

Seems that the content provider for Picasa albums doesn&#39;t have a _data field.

The code for getting the location is:

&lt;pre&gt;
// imageUri is the Uri from above.
String[] proj = { MediaStore.Images.Media.DATA };
Cursor cursor = context.getContentResolver().query(imageUri, proj,null, null, null);
int column_index = cursor.getColumnIndexOrThrow(MediaStore.Images.Media.DATA);
cursor.moveToFirst();

String filePath = cursor.getString(column_index);
cursor.close();
&lt;/pre&gt;

The only columns that seem to be supported for this image are:
[user_account, picasa_id, _display_name, _size, mime_type, datetaken, latitude, longitude, orientation]

How do we get the actual location of this image. And if we are not supposed to work with this image, **these images shouldn&#39;t be shown to the user in the first place.**

The Intent to launch the gallery app is:
&lt;pre&gt;
Intent intent = new Intent();
intent.setType(&quot;image/*&quot;);
intent.setAction(Intent.ACTION_GET_CONTENT);
&lt;/pre&gt;

All Android Contentprovider Solutions on Gang of Coders

Total of 19 Android Contentprovider Solutions

android - CursorLoader & SQLite without Content Provider