Search Unity

  1. Unity 2019.4 has been released.
    Dismiss Notice
  2. Good news ✨ We have more Unite Now videos available for you to watch on-demand! Come check them out and ask our experts any questions!
    Dismiss Notice
  3. Ever participated in one our Game Jams? Want pointers on your project? Our Evangelists will be available on Friday to give feedback. Come share your games with us!
    Dismiss Notice

Feedback Unity Analytics Package hierarchy?

Discussion in 'Unity Analytics' started by Yanka33, Jun 14, 2020.

  1. Yanka33

    Yanka33

    Joined:
    Oct 12, 2015
    Posts:
    10
    Hi there,

    I am writing this thread for the tech team maintaining the Unity Analytics Package.

    Comparing to the other packages maintained by Unity, I cannot help but to notice that the hierarchy of the Unity Analytics package is quite a mess.

    In the guidelines for creating a package for the Package Manager, there is a clear hierarchy to respect as well as some specific Assembly definition files to declare: https://docs.unity3d.com/Manual/cus-layout.html

    However, Unity Analytics does not respect this hierarchy at all and does not declare any Assembly definition file!
    This may seem like nothing but it is actually quite an issue for people who wants to create a custom package for the PackageManager and declare in its Assembly definition file a dependency to Unity Analytics. Today, this is simply impossible, leading to the impossibility to build the project.

    Please, clean the hierarchy, declare properly the Assemblies for the package!
     
    JeffDUnity3D likes this.
unityunity