Mobile Platform as a Service:Overview

mPaaS depends on several third-party SDKs. When you integrate mPaaS, dependency conflicts may occur between the mPaaS SDK and other third-party libraries in your project.

To resolve potential conflicts, mPaaS lets you remove its internal third-party SDKs. For removal methods, see:

• Native AAR method

• Component-based integration method

The versions of third-party libraries used by mPaaS are highly stable and secure. If you remove a library that mPaaS depends on and use a different version, you must thoroughly test your application to ensure all features remain stable.

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