Adding multiple file providers in Android application

Question

guys, I am working on an android application for which I need external application dependency(.aar file) library application has its own file provider and my application have its own.

library work well when I run it as a separate app but when I include it my application then camera functionality not working. I get the following error

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

following the manifest file of the 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/file_paths" />
        </provider>

and the following is a manifest file of the lib module

<provider
            android:name="android.support.v4.content.FileProvider"
            android:authorities="com.ma.bot.provider"
            android:exported="false"
            android:grantUriPermissions="true">
            <meta-data
                android:name="android.support.FILE_PROVIDER_PATHS"
                android:resource="@xml/file_paths" />
        </provider>

both application and lib module have different package name how I add this 2 file providers into the application I also try including multiple file providers using, but I get XML parse error on app compilation.

android:authorities="${applicationId}.provider;com.ma.bot.provider"

how to solve this.

dev_swat · Accepted Answer · 2018-11-28 05:12:38Z

37

Guys I found solution on this link Possible to use multiple authorities with FileProvider?

Basically problem is my library and application have same name android.support.v4.content.FileProvider so it colliding in manifest merger, to avoid this I need to defile empty class extending File provider and use it provider name

<provider
            android:name="com.MAG.MAGFileProvider"
            android:authorities="${applicationId}.provider;"
            android:exported="false"
            android:grantUriPermissions="true">
            <meta-data
                android:name="android.support.FILE_PROVIDER_PATHS"
                android:resource="@xml/file_paths" />
        </provider>

and declare class like this

import android.support.v4.content.FileProvider;
public class MAGFileProvider extends FileProvider
{
    //we extend fileprovider to stop collision with chatbot library file provider
    //this class is empty and used in manifest
}

answered Nov 28, 2018 at 5:12

dev_swat

1,3441 gold badge13 silver badges29 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Himanshu Mori Over a year ago

it worked for me. when I am using this for library android:name="android.support.v4.content.FileProvider" android:authorities="com.library.provider" and this in main app manifest android:name="com.MAG.MAGFileProvider" android:authorities="${applicationId}.provider;"

Karen Over a year ago

where does the class file get created?

Oleksandr Nos Over a year ago

best answer ever!

Collectives™ on Stack Overflow

Adding multiple file providers in Android application

1 Answer 1

3 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related