Mobile Platform as a Service:Resolve Amap dependency confilct

mPaaS bundles the AMAP Map SDK. If your app targets Google Play Store and also integrates an official AMAP SDK approved by Google, the two copies of the AMAP Map SDK conflict. Remove the bundled SDK from mPaaS to resolve the conflict.

How the dependency conflict occurs

mPaaS ships with AMAP Map SDK 5.2.1_20190114. If your app includes a separate, Google-approved AMAP SDK alongside mPaaS, the Android build system detects two copies of the same library. This causes a dependency conflict that prevents your app from being published to Google Play Store.

To resolve the conflict, exclude the bundled AMAP Map SDK from mPaaS and declare your own AMAP SDK as the sole dependency.

Exclude the bundled AMAP Map SDK

1. Identify the version of the AMAP Map SDK bundled with mPaaS, and use this version (or a Google-approved version) as your app's AMAP dependency.

   'com.alipay.android.phone.mobilecommon:AMap-2DMap:5.2.1_20190114@jar'

2. Note the group:artifact coordinates of the bundled AMAP Map SDK.

   'com.alipay.android.phone.thirdparty:amap3dmap-build'

3. Exclude the AMAP Map SDK from mPaaS using the configuration that matches your integration method.

   • AAR integration — add the following to your app-level build.gradle:

     configurations {
     all*.exclude group:'com.alipay.android.phone.thirdparty', module: 'amap3dmap-build'
     }

   • Portal & Bundle integration — add the following to the mpaascomponents block in your build.gradle:

     mpaascomponents {
     excludeDependencies = [
        "com.alipay.android.phone.thirdparty:amap3dmap-build"
     ]
     }