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
constructor FileProvider in class FileProvider cannot be applied to given types #2978
Comments
Please, Fix this. |
I have the same issue. Downgrading to |
I have the same issue |
no need to go all the way down to On |
I have the same issue |
But I can't install 12.2.1. The newest version is 12.2.0. |
@willTerner it's |
I have the same issue with "react": "18.2.0",
"react-native": "0.71.8",
"react-native-webview": "^12.2.0" Error Message
|
I have the same issue with |
The issue seems to be that 12.2.0 uses a
|
I have the same issue |
I have the same issue in my react-native application. |
Fixed by installing 12.1.0 |
Yes, there are 2 possible fixes that I know:
|
same issue for me |
Hello everyone .. This is caused by 75e7801 which I merged a couple of days ago to mitigate large number of crashes reported in some OEM devices. The motivation behind the fix was to leverage the change https://android-review.googlesource.com/c/platform/frameworks/support/+/1978527 which added a workaround to the androidx.core module to avoid stripping the File provider metadata. The fix to androidx.core is available from https://developer.android.com/jetpack/androidx/releases/core#core-1.8.0-alpha06 (which was released more than an year ago) onwards. Could you folks upgrade to this version to avoid the crash ? Transitive dependency can be explicitly resolved as @mlazari suggested above #2978 (comment) Thanks ! |
@mganandraj can you pin this issue? |
getting the same issue.
|
add this in Build.gradle file
in app/build.gradle file
|
I don't want to change build.gradle files because in the future, when you have to update react-native, there will be problems with editing these files. |
Actually in Build.gradle we are using the latest version ,by default react-native us using old version .So, when we update in future we will not get any error. |
Hi there, Use the tilde on your dependency version range to avoid getting next minor version like |
I'm looking into making the usage of the new construction conditional on the availability of the new version of android modules .. Please hold on. |
Hi,
After u can do a |
OK. yeah unsure when react-native and all modules will support 1.8.0 and up. |
@mganandraj I'll revert while we find a solution to fix most people issues, keeping this open for follow up |
Hi @Titozzz Sure, please go ahead with the revert. I will continue investigating on getting this change back in a way that works with all versions of androidx libraries. We should also try to get react native to transitive depend on newer androidx versions. For short term, I can add a local patch. (By the way, Sorry for introducing this situation. I didn’t realize that so many codebases are still referring to the old version of androidx.core library.) |
Upping this, 12.2.0 doesn't work for me either. Same error as OP |
@arihirsch Update to 12.2.1 or newer (latest is 13.2.2 now), this issue was fixed in 12.2.1 |
Hello 👋, this issue has been opened for more than 2 months with no activity on it. If the issue is still here, please keep in mind that we need community support and help to fix it! Just comment something like still searching for solutions and if you found one, please open a pull request! You have 7 days until this gets closed automatically |
Repository here
Versions
Steps are:
Error message:
The text was updated successfully, but these errors were encountered: