Sending device identifiers about crisp-sdk-android HOT 3 OPEN

Hi @nfonjeannoel and thank you for your feedback.

The only thing which seems to be the closest of what Google says is our User-Agent used for REST/WebSocket calls which contains a reference to Build.VERSION.INCREMENTAL, I don't know if this is it or if this is against Google Play policies (it does not seem to as this is a software "id", only hardwares one are prohibited, see Best practices for unique identifiers
), it seems awkward as we cannot identify a device through this info as this is the build number of the Android OS not the device serial number or IMEI or MAC Address...
Documentation says about it :

The internal value used by the underlying source control to represent this build. E.g., a perforce changelist number or a git hash.

We build the User-Agent upon:

• app label,
• versionCode,
• Android version (Build.VERSION.RELEASE),
• Android build (Build.VERSION.INCREMENTAL).

It is formatted as APP_LABEL/APP_VERSION_CODE (Version ANDROID_VERSION (Build ANDROID_BUILD)).
On our app on an Android 13 Emulator it appears as Crisp/500052 (Version 13 (Build 10940250)).

Build number can be found in Settings > About menu of the phone (see below)

Maybe this is the word Build which raises a warning on their side or simply its usage? This is the first time we get this warning from our users since the 1st release of the SDK and this User-Agent was here since the beginning ^^"

Can you ask Google if this is this is the issue with your app? If this is it, I will remove the Build.VERSION.INCREMENTAL from the User-Agent.

Best regards.

from crisp-sdk-android.

thank you @Doc1faux
I will message them and get confirmation. Thanks

from crisp-sdk-android.