question

This is a big issue for us as well, many players denying the permission to share contacts (understandably so). Is it for sure that your Monday release will fix this. Also, if we disable the unique identifier, how can we get the Device ID "via other means"?

This is a major issue for us as well, with many players denying the permission. Is it for sure that you will fix this in the Monday release, and how can we get the device ID "via other means"?

@Giacomo, @Cadrick Loh and to anyone else whom is following this thread.

I wanted to take a moment to clarify a couple of things for you..

Prior to the fix, we implemented deviceUniqueIdentifier as a means to get device information as part of our data gathering. This is not part of any login API call in the SDK - it was being used for simple data gathering. Unfortunately, a change the way Unity uses deviceUniqueIdentifer to get that information, it now triggers this permission pop-up.

Our fix removes the dependency on deviceUniqueIdentifier for Android. This solves the issue and we are now using JNI to acquire the DeviceId natively from the Java layer. Accessing this DeviceId does not trigger any special permissions.

As for Logging in with a DeviceId, you should never use deviceUniqueIdentifier with LoginWithAndroidId. Even prior to the recent Unity change, that ID was always unreliable (under certain circumstances, it falls back to various other identifiers on Android). That's why we've always advised getting the ID natively.

To do this there is a great thread about this on the Unity Answers Forum that shows a good way to natively get the Android DeviceId (this is basically the same code we use):

#if  UNITY_ANDROID && !UNITY_EDITOR

AndroidJavaClass up = new AndroidJavaClass ("com.unity3d.player.UnityPlayer"); 
AndroidJavaObject currentActivity = up.GetStatic<AndroidJavaObject> ("currentActivity");
AndroidJavaObject contentResolver = currentActivity.Call<AndroidJavaObject> ("getContentResolver");

AndroidJavaClass secure = new AndroidJavaClass ("android.provider.Settings$Secure");
string android_id = secure.CallStatic<string> ("getString", contentResolver, "android_id");


#endif

This should always be performed with the pre-processor directive #if UNITY_ANDROID && !UNITY_EDITOR.

Outside the login flow, you can use the fix above (DISABLE_UNIQUEIDENTIFIER) to disable that check in our data gathering code, or update to the new SDK we'll be posting next week.