FileProvider NPE null object reference

Question

Hi I'm currently experiencing error on starting an intent due to FileProvider causing NPE. I followed the steps provided here but I still got the error:

Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.XmlResourceParser android.content.pm.PackageItemInfo.loadXmlMetaData(android.content.pm.PackageManager, java.lang.String)' on a null object reference

I am not sure as well if the provider_paths.xml is being used here. Here's my code so far:

Manifest:

<application>... <provider
            android:name="android.support.v4.content.FileProvider"
            android:authorities="${applicationId}.provider"
            android:exported="false"
            android:grantUriPermissions="true">
            <meta-data
                android:name="android.support.FILE_PROVIDER_PATHS"
                android:resource="@xml/provider_paths"/>
        </provider></application>

res/xml:

<?xml version="1.0" encoding="utf-8"?>
<paths xmlns:android="http://schemas.android.com/apk/res/android">
    <external-path name="external_files" path="."/>
</paths>

code:

Uri uri=FileProvider.getUriForFile(context, BuildConfig.APPLICATION_ID+".provider", file);

the itself seems to be the cause of error here.

I'm not sure why I get a down vote on this question. I know some will say this is a duplicate but I already checked on every solution I can find here and it all says the same. For now I opt to just use: StrictMode.VmPolicy.Builder builder = new StrictMode.VmPolicy.Builder(); StrictMode.setVmPolicy(builder.build()); sad thing SO community. :( — KaHeL, Jun 29 '17 at 07:35

score 0 · Answer 1 · answered Dec 09 '18 at 13:23

BuildConfig.APPLICATION_ID should return your packagename, however, in my case it returned "android.support.v4". I consider using getPackagename() and it will work just fine!

So just change

FileProvider.getUriForFile(this,
                            BuildConfig.APPLICATION_ID + ".provider", file);

to:

FileProvider.getUriForFile(this,
                            getPackagename() + ".provider", file);

score 0 · Answer 2 · answered Dec 22 '18 at 09:06

Refer to this link for your answer. enter link description here

First, this:

android:authorities="${applicationId}.fileprovider"

you are using this:

FileProvider.getUriForFile(this,
                            BuildConfig.APPLICATION_ID + ".provider", file);

chabge this :

FileProvider.getUriForFile(this,
                            BuildConfig.APPLICATION_ID + ".fileprovider", file);

Since I don't know which of those is what you really want, I cannot suggest a fix.

SANAT · Answer 3 · 2017-06-29T08:51:57.247

-1

I am using this :

Manifest :

<provider
            android:name="android.support.v4.content.FileProvider"
            android:authorities="${applicationId}.provider"
            android:exported="false"
            android:grantUriPermissions="true">
            <meta-data
                android:name="android.support.FILE_PROVIDER_PATHS"
                android:resource="@xml/provider_paths"/>
        </provider>

XML file :

<paths xmlns:android="http://schemas.android.com/apk/res/android">
    <external-path name="media_folder" path="." />
</paths>

In Java :

FileProvider.getUriForFile(this,
                                BuildConfig.APPLICATION_ID + ".provider", file);

edited Jun 29 '17 at 08:51

answered Jun 29 '17 at 07:23

SANAT

8,489
55
66

Sadly, it is just the same thing I used. – KaHeL Jun 29 '17 at 07:36
Glad to hear that but it is not for me. I'm using device working with Android N – KaHeL Jun 29 '17 at 08:41
It is useful in android n only. Please try using this – SANAT Jun 29 '17 at 08:42

FileProvider NPE null object reference

3 Answers3