Solve conflict with dependency on Amap location - Mobile Platform as a Service

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.

Important

The 10.1.32 baseline does not support self-integration of the positioning SDK, so there is no such conflict.

Solution

Remove the built-in AMAP Positioning SDK from mPaaS.

Procedure

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.
```
'com.alipay.android.phone.mobilecommon:AMapSearch:6.1.0_20180330@jar'
'com.alipay.thirdparty.amap:amap-location:4.7.2.20190927@jar'
```
Get the group:artifact information for the AMAP Positioning SDK used by mPaaS.
```
'com.mpaas.group.amap:amap-build'
```

Remove the AMAP Positioning SDK from mPaaS.

AAR method

configurations {
all*.exclude group:'com.mpaas.group.amap', module: 'amap-build'
}

Portal & Bundle

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