All Products
Search
Document Center

Mobile Platform as a Service:Resolve AMap location conflicts

Last Updated:Feb 04, 2026

mPaaS includes a built-in AMap location SDK. A location conflict occurs if you also integrate the official version of the AMap SDK approved for the Google Play marketplace.

Important

Baseline 10.1.32 does not support integrating a location SDK. Therefore, this conflict does not occur.

Solution

Remove the built-in AMap location SDK from mPaaS.

Procedure

  1. Confirm the version of the AMap location SDK that mPaaS uses. This lets you select an identical or a similar approved version.

    'com.alipay.android.phone.mobilecommon:AMapSearch:6.1.0_20180330@jar'
    'com.alipay.thirdparty.amap:amap-location:4.7.2.20190927@jar'
  2. Obtain the group:artifact information for the AMap location SDK that mPaaS uses.

    'com.mpaas.group.amap:amap-build'
  3. Remove the mPaaS AMap location SDK.

    • AAR method

      configurations {
      all*.exclude group:'com.mpaas.group.amap', module: 'amap-build'
      }
    • Component-based (Portal & Bundle)

      mpaascomponents {
      excludeDependencies = [
         "com.mpaas.group.amap:amap-build"
      ]
      }