Resolve AMap location SDK dependency conflicts when integrating the official SDK - Mobile Platform as a Service - Alibaba Cloud - Mobile Platform as a Service

mPaaS includes a built-in AMap location SDK. If you also integrate the Google Play-approved version of the AMap SDK, both SDKs share the same group:artifact identifier, causing Gradle to fail when it cannot resolve the version conflict. To fix this, remove the built-in AMap location SDK from mPaaS before your build.

Important

Baseline 10.1.32 does not support integrating a location SDK, so this conflict does not occur on that baseline.

Remove the built-in AMap location SDK

Steps

Identify the AMap location SDK version bundled in mPaaS, then select a matching or compatible version from the Google Play marketplace.

The bundled versions are:
```
'com.alipay.android.phone.mobilecommon:AMapSearch:6.1.0_20180330@jar'
'com.alipay.thirdparty.amap:amap-location:4.7.2.20190927@jar'
```
Note the group:artifact coordinates for the built-in AMap location SDK:
```
'com.mpaas.group.amap:amap-build'
```

Exclude the built-in AMap location SDK using the configuration that matches your integration type.

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"
]
}