[ISSUE] On iOS, your device class generates ambiguous statement with Unity's one about appcenter-sdk-unity

[annakocheshkova]

Hi there! The reason we have this class is we have identically-named ones in native SDKs.
With namespaces, it shouldn't be an issue. Is that so with asmdef-s?

[liszto]

I just create a non asmdef project from scratch.
So I just use AppCenter Editor Extension to download your package.
Then I create this script :

using UnityEngine;
using UnityEngine.iOS;
using Microsoft.AppCenter.Unity;

public class TestDevice : MonoBehaviour
{
    // Start is called before the first frame update
    void Start()
    {
		Device test = new Device();
    }
}

and Visual Studio is not happy with this cause he doesn't know which one to use :

Erreur CS0104 'Device' is an ambiguous reference between 'Microsoft.AppCenter.Unity.Device' and 'UnityEngine.iOS.Device' Assembly-CSharp D:\Project\App-asmdef\New Unity Project\Assets\Scenes\TestDevice.cs

Ambiguous reference is still present so as I supposed it was not due to asmdef but just in cased I prefered to test it ;)

[annakocheshkova]

Oh I see. So you use the both Device classes in one file and then yeah, it complains. Definitely, we should look for a way to name this better.

[DmitriyKirakosyan]

As we do not have plans to add support for this feature in the next year, I'm closing the issue.