All Products
Search
Document Center

Solve conflict with dependency on Amap location

Last Updated: Mar 10, 2021

Conflict description

mPaaS is built with the AMAP Positioning SDK. If your app needs to be launched in Google Play Store and also integrates with the official version of the SDK provided by AMAP that can be approved by Google, there will be a conflict with AMAP Positioning.

Solution

Remove the built-in AMAP Map SDK from mPaaS (10.1.32 baseline not supported).

Procedure

  1. Confirm the version of the AMAP Positioning SDK used by mPaaS so that you can select the same or a similarly reviewed and approved version.

    1. 'com.alipay.android.phone.mobilecommon:AMapSearch:6.1.0_20180330@jar'
    2. 'com.alipay.thirdparty.amap:amap-location:4.7.2.20190927@jar'
  2. Get the group:artifact information for the AMAP Positioning SDK used by mPaaS.

    1. 'com.mpaas.group.amap:amap-build'
  3. Remove the AMAP Positioning SDK from mPaaS.

    • AAR method

      1. configurations {
      2. all*.exclude group:'com.mpaas.group.amap', module: 'amap-build'
      3. }
    • mPaaS Inside and Portal & Bundle

      1. mpaascomponents {
      2. excludeDependencies = [
      3. "com.mpaas.group.amap:amap-build"
      4. ]
      5. }