Overview

mPaaS depends on several third-party SDKs, so dependency conflicts may occur between the mPaaS SDK and other third-party libraries in your project during integration.

To resolve conflicts, you can remove the internal third-party SDKs bundled with mPaaS. For removal methods, see:

• Native AAR method

• Component-based integration method

The third-party libraries bundled with mPaaS are selected for stability and security. If you remove a bundled library and replace it with a different version, thoroughly test your application to ensure that all features work as expected.

If you encounter a dependency conflict, see the following solutions:

• Resolve AMAP Location conflicts

• Resolve AMAP Maps conflicts

• Resolve conflicts with Security Guard

• Resolve utdid conflicts

• Resolve Alipay SDK conflicts

• Resolve wire/okio conflicts

• Resolve fastjson conflicts

• Resolve android support conflicts

• Resolve libc++_shared.so conflicts

• Resolve libstlport_shared.so conflicts

• Resolve libcrashsdk.so conflicts