All Products
Search
Document Center

Mobile Platform as a Service:Resolve libcrashsdk.so conflicts

Last Updated:Feb 02, 2026

Conflict description

Using mPaaS with other third-party SDKs, such as the Umeng SDK, causes a libcrashsdk.so conflict.

[ERROR] :more than one file named : libcrashsdk.so in below 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

You can remove libcrashsdk.so from the mPaaS UC kernel.

Procedure

  1. Obtain the group:artifact information for the SDK that mPaaS uses.

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

    • For the AAR connection type:

      configurations {
          all*.exclude group:'com.mpaas.uc.crash', module: 'uccrash-build'
      }
    • For the mPaaS Inside or component-based (Portal&Bundle) connection type:

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