Resolve libcrashsdk.so conflicts when integrating with third-party SDKs - Mobile Platform as a Service - Alibaba Cloud - Mobile Platform as a Service

If mPaaS and another third-party SDK both bundle libcrashsdk.so, exclude the mPaaS crash module to resolve the conflict.

Conflict description

A libcrashsdk.so conflict occurs when mPaaS is used alongside other third-party SDKs such as the Umeng SDK.

[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

Remove libcrashsdk.so from the mPaaS UC kernel to resolve the conflict.

Procedure

Obtain the group:artifact information for the SDK that mPaaS uses.
```
'com.mpaas.uc.crash:uccrash-build'
```

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"
    ]
}