Fileprovider conflict resolution
Because the Maven service of Weibo sharing SDK is abnormal, the Maven automatic integration fails, so the AAR file of Weibo 10.10.0 is downloaded for local integration. Error report after adding project android:resource= “@xml/file_ XXX “reuse does not work
2. Add tools:replace= “ android:resource ”Go to the following figure
<provider
android:name="androidx.core.content.FileProvider"
android:authorities="${applicationId}.fileProvider"
android:exported="false"
android:grantUriPermissions="true"
tools:replace="android:authorities">
<meta-data
android:name="android.support.FILE_PROVIDER_PATHS"
android:resource="@xml/file_xxx"
tools:replace="android:resource" />
</provider>
solve
Read More:
- CONDA reports an error: conflict package conflict
- Android solution to the conflict of calling ontouch and onclick at the same time
- 0xc0000005: solution to access conflict when writing to location 0x00000000
- Docker delete error response from daemon: Conflict: unable to delete xxxxx solution
- Android dependency conflict resolution
- Hash conflict and four solutions
- Resolve Tree Conflict SVN
- [details] jar conflict resolution in Maven (personal test)
- Docker compose reports an error and multiple containers conflict
- Docker error response from daemon: Conflict: unable to deletexxxxx
- 0xc0000005: an access conflict occurred while reading location 0x00000020
- CMake_ Compiling VTK_ 9.0.0 running vtkcommoncolor DLL has access conflict
- C language problem: 0xc0000005: access conflict occurred when writing to location 0xffffcc.
- Opencv: 0xc0000005: an access conflict occurred while reading location 0x0000000010
- Three possibilities of “unhandled exception: 0xc0000005: access conflict when reading location 0x00000000”
- Error response from daemon: Conflict: unable to delete 8598c91556dc (must be forced)
- Spring jacjson version conflict “nosuchme” thodError:com.fasterxml.jackson.databind.ObjectMapper.canSerialize “
- [debug notes] pointer error when STD:: vector is used in VTK “access conflict when reading location XXX”
- Bug resolution of 0xc0000005: access conflict occurred when reading location of 0x00000000.