All Products
Search
Document Center

Mobile Platform as a Service:Solve conflict with libcrashsdk.so

Last Updated:Sep 15, 2023

Conflict description

A libcrashsdk.so conflict may occur if you use a third-party SDK such as Umeng SDK while using mPaaS.

[ERROR] :more than one file named : libcrashsdk.so in the following files
C:\Users\Administrator\.gradle\caches\modules-2\files-2.1\com.mpaas.uc.crash\uccrash-build\1.0.0.201221171651\d347c79b8091adc68c33e1ca04b702b1c85888ca\uccrash-build-1.0.0.201221171651.jar
C:\Users\Administrator\.m2\repository\com\xinmei\etrust\bundleone\bundleone-build\1.0.0\bundleone-build-1.0.0-raw.jar

Solution

Remove libcrashsdk.so from the UC kernel of mPaaS.

Procedure

  1. Get the group:artifact information for the third-party SDK used by mPaaS.

    'com.mpaas.uc.crash:uccrash-build'
  2. Remove libcrashsdk from the UC kernel of mPaaS.

    • Native AAR integration method:

      configurations {
          all*.exclude group:'com.mpaas.uc.crash', module: 'uccrash-build'
      }
    • mPaaS Inside integration method method or componentized integration method:

      mpaascomponents {
          excludeDependencies = [
             "com.mpaas.uc.crash:uccrash-build"
          ]
      }