-
-
Notifications
You must be signed in to change notification settings - Fork 446
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File provider is preventing the app from launching on earlier Android versions #693
Comments
I wish to work on this. |
This issue still exists.I am unable to proceed forward due to this. |
@sowmya9029 You are experiencing this issue while the app is opening right? |
This issue can be closed. Cannot see how to do it on Fasthub though. |
Hi Please follow the build error and see what is crushes. In my case I changed every "android.aaa.bbb.ccc" which is incompatible or old libraries with "androidx.aaa.bbb.ccc". To see androidx version libraries search for google, you can find them in android's web page. In my case changing those libraries removed all build fails but it was not enough for me because when I tried to run my app on device then it gave me "android.support.v4.content.FileProvider" this error. I was changed all of my android.support.v4.content.FileProvider libraries with the new androidx.core.content.FileProvider but what was crushing now ? even while building gives no any error. Finally I figured out it, I just needed to change one library with new version too and here is steps: Click to AndroidManifest.xml look at the bottom of the files page you gonna see "Text" and "Merged Manifes" then click to "Merged Manifest" -> Search for "android.support.v4.content.FileProvider" then change it with "androidx.core.content.FileProvider" Now you should get to go without any error. |
Now that we've migrated to androidx this should be fixed. Feel free to reopen/comment for reopening. |
am getting this exception after migrate to AndroidX |
Tested on APIs 16 and 18.
From what I can understand, "FileProvider" has been added to the EasyImage library which is causing this problem.
The text was updated successfully, but these errors were encountered: