I do formally withdraw the Mindset comment, as it was a personal observation. I apologize for putting you on the defensive, Stephan. Where I encountered this the most, was in Unity 2017.3 & .4 versions. I noticed today that Unity 2018.2 now actually shows the packages that the project will use (whether you added them or not, apparently). I jut installed 2018.2 last night, and I didn't see it because my project was sprawled out pushing it out of view. With 2018.2... It only shows the one package for TMPro, and it does compile and run correctly. Maybe that part of the team fixed how it's addressed? (Speculating there.) In 2018.2, here are the packages... (Trimmed down some...) ... "com.unity.package-manager-ui": "1.9.11", "com.unity.purchasing": "2.0.3", "com.unity.textmeshpro": "1.2.4", "com.unity.modules.ai": "1.0.0", "com.unity.modules.animation": "1.0.0", "com.unity.modules.assetbundle": "1.0.0", ... I do apologize, at this hour, I am not exactly 100% sure which project in my project drive has an older version of unity, that used TMPro. Depending on how busy work is, I'll try to look for it tomorrow. What I do remember about it: I had installed the TMPro package from the preview area, as it wasn't in the Unity Package manager yet. That put it into my assets directory initially. Then, when I installed Unity 2017.3? I had issues, because I thought it would update it correctly, when I saw that it was part of the new package manager loadout. So, I deleted it out of the assets directory. And I continued to have issue, even after that and after installing 2017.4. I tried removing the UPM package for it, and it was still broken. It had referenced the packages in the cache, too. (Weird behavior, but hey, why not?) I tried recreating the project, and it worked ok until I tried to use any of the TMPro items, and it wanted to install the extras. (And I said, okay - make this work!) Boom. Breakage. I did that twice, with deleting every TMPro related item in the assets directory... to no avail. Then I searched for help, encountered the forums, and immediately facepalmed when I was told, by you, to "Delete the folder in the assets directory" as the official "this fixes everything" answer. (Curious side note here, this is also when I learned that comcast has a really crappy upload speed... As I really wanted to show you the project in its entirety so you could see it yourself.) I recreated the project yet again, and had the same set of errors, so I decided to eradicate anything TMPro from my computer, and find a different way to do things. That's when I found the Unity Package manager cache. I found multiple copies of the TMPro asset in there, and I deleted them all, as I had already "uninstalled the packages" in UMP. And, wow... that worked. (I wasn't as eager to give up on it, as I thought I was, as I gave it another try.) With only the one package in the cache area, and available... it worked... So, I marked it as the answer and left it. As a disclosure, I've not tried TMPro in the now new project (even though it's listed under referenced packages, and I didn't tell Unity to even use it. It's just there, after I installed 2018.2). Having the thing work, even without the emoticons, I'm good with. And, I can't say that I am eager to break things just to go "See!!! I told you it didn't work!!!" as, that's not conducive to getting things built. Hopefully that will give a road map? I dunno if the UPM team will address it, as I would hazard to think that in Listing the Referenced packages (as they do in 2018.2) they would remove duplicate packages and enforce some checking routines... So, maybe it's only broke in 2017? Good reason to update, right? lol.