Huawei Mobile Services SDK violation Device and Network Abuse policy

Update:

Note: If you have confirmed that the latest SDK version is used, before submitting a release to Google, please check the apks in all Testing track on Google Play Console(including Open testing, Closed testing, Internal testing). Ensure that the APKs on all tracks(including paused track) have updated to the latest HMS Core SDK.

HMS Core SDKs have undergone some version updates recently. To further improve user experience, update the HMS Core SDK integrated into your app to the latest version.

Required versions for cross-platform app development:

If you have any further questions or encounter any issues integrating any of these kits, please feel free to contact us.

If you have dependencies that can be replaced with Google compatible equivalent dependencies then this could be a possible solution to manage both in one code base.

Using app flavours I was able to separate my GMS and HMS dependencies. In your app level build.gradle file you can create product flavour like so

android {
    flavorDimensions "platforms"
    ...
    productFlavors {
        gms {
            dimension "platforms"
        }
        hms {
            dimension "platforms"
        }
    }
    ...
}

More on product flavors here. And then you can specify if a dependency should be part of the flavour by prefixing it to the keyword implementation under dependencies.

dependencies {
    ...
    gmsImplementation 'com.google.android.gms:play-services-maps:18.0.2'
    hmsImplementation 'com.huawei.hms:maps:5.0.0.300'
    ...
}

I then went a bit further by wrapping the usage of each dependency in a class that is available in both flavours but the implementation differs based on the dependency's requirements.

com.example.maps.MapImpl under src>hms>java
and
com.example.maps.MapImpl under src>gms>java

So I am free to use the wrapper class anywhere without worrying about the dependency mismatch.

The HMS dependency is no longer part of the GMS build variant so I would be able to upload that to the Google playstore.

I solved it by doing similar to what @Daniel has suggested to avoid such worries in the future:

1. Create different product flavors in your app level Gradle file:

android {
    ...

    flavorDimensions 'buildFlavor'

    productFlavors {
        dev {
            dimension 'buildFlavor'
        }

        production {
            dimension 'buildFlavor'
        }


        huawei {
            dimension 'buildFlavor'
        }
    }
}

2. Restrict the Huawei related dependencies so they're only available for Huawei product flavor:

    huaweiImplementation "com.huawei.hms:iap:3.0.3.300"
    huaweiImplementation "com.huawei.hms:game:3.0.3.300"
    huaweiImplementation "com.huawei.hms:hwid:5.0.1.301"
    huaweiImplementation "com.huawei.hms:push:5.0.0.300"
    huaweiImplementation "com.huawei.hms:hianalytics:5.0.3.300"
    huaweiImplementation "com.huawei.hms:location:5.0.0.301"

3. Since dev and production flavors are not going to have Huawei dependencies now, you may get build errors for the Huawei related classes that you use in your app.

For that I create dummy classes with the same packages tree as Huawei, for instance:

app > src > dev > java > com > huawei > hms > analytics > HiAnalytics.kt

class HiAnalytics {

    companion object {

        @JvmStatic
        fun getInstance(context: Context): HiAnalyticsInstance {
            return HiAnalyticsInstance()
        }
    }
}

4. This solves the Cannot resolve symbol error when trying to import Huawei classes in your main, dev, or production flavors and you can import those classes anywhere:

import com.huawei.hms.analytics.HiAnalytics

Now if you change the build variant to dev, you should have access to the dummy classes in your app. If you change it to huawei, you should be able to access the classes from Huawei dependencies.

UPDATE 06/04/2022

Huawei released a new version of their SDK : 3.4.0.300

3.4.0.300 (2022-03-04) New Features

• Real-time translation: Added Afrikaans to the list of languages supported. (Note that this language is available only in Asia, Africa, and Latin America.)

Modified Features

• Deleted the capability of prompting users to install HMS Core (APK).
• Modified the SDK privacy and security statement. Updated the SDK
• versions of all subservices.

For me, since I've migrated to Google ML Kit, I will wait till August, then I will switch back to Huawei ML Kit to make sure Google will not remove or suspend my apps.

Old answer :

I used to love the HMS ML kit, but because of this issue, I'm aware that Google will one day completely suspend my apps because I'm using HMS services, and even if Huawei fixes the issue, we'll have to wait 120 days to find out if we're safe.

In my case, I'm using the HMS Segmentation ML Kit. I've just switched to Google Selfie Segmentation ML. I will wait till 120 days have passed and see if the issue is still persisting for other developers. If not, I will switch back to the HMS Kit.

I just use hms push when upload to huawei. i fixed by commenting hms services in build.gradle and app/build.gradle when to upload to playstore. Then, I uncomment if upload to huawei.

//apply plugin: "com.huawei.agconnect"

apply plugin: 'com.google.gms.google-services'

//implementation 'com.huawei.hms:push:5.3.0.304'.  

The solution to the problem is to update the dependencies like in this link.

With this update, the ability to prompt users to install HMS Core (APK) has been removed.

https://developer.huawei.com/consumer/en/doc/development/hmscore-common-Guides/hmssdk-kit-0000001050042513#section20948233203517