You do not have entitlement for this package.

georgeq · February 20, 2020, 9:17pm

[Unity 2020.1.0a21.2690]
Any explanation for this?

pbrito_unity · March 1, 2020, 12:30am

I have the same problem.
Unity 2020.1.0a025

LeonhardP · March 2, 2020, 1:13pm

Could you please send us a bug report about this issue so we can have a look at your logs?

georgeq · March 2, 2020, 4:50pm

At the moment this occurred, I had 2 copies of the same project open. I checked for the logs, but the folder was empty.
I checked for logs on other projects, but I couldn’t find any logs of any of the projects I opened with 2020.1.0a21.

LeonhardP · March 2, 2020, 4:57pm

This is where the logs are stored: Unity - Manual: Log files

They’re automatically attached to bug reports, so reporting a bug for the issue would be the most straightforward way to share them with us.

georgeq · March 2, 2020, 5:42pm

On older versions (in Windows) logs were stored on C:\Users\username\AppData\LocalLow\companyname\projectname I think that made more sense, at least for the way I work in Unity. I don’t know if other people out there have similar work flows, but in recent times I often work on small projects, and I often have 2, 3 or more instances of Unity running at the same time, I also often have 2 versions of Unity open at the same time. According to this document, the logs are now stored in a single file, so what happens in a situation like this?.. The only way to deal with it would be to have all instances of the editor writing to the log file in a coordinated way, but if that’s the case, the log can easily become a huge mess of data. In my opinion, every instance of the editor should have its own log, so in case of a bug report you could send only the information relevant to the problem at hand, and not a huge bunch of unrelated stuff… but that’s just my opinion.

Baste · March 3, 2020, 9:20am

Gonna second that. @LeonhardP , you really ought to have CompanyName\ProductName be a part of both the packman and the editor logs.

The irony here is that the point where this becomes a problem is when I actually need the log. If there’s some bug, and I want to create a bug report, I create a fresh project to repro the bug. I don’t necessarily close the old project. Does one of the editors just not get to write to the editor.log? Does it get mangled? None of those are great.

Octo_Games · March 3, 2020, 10:30pm

I am having this exact same issue, but I guess I should have been wary of an Alpha build.

Edit: I fixed it by restarting Unity. Hopefully, it works for you too as a short-term fix.

LeonhardP · March 4, 2020, 3:11pm

These points came up in the past as well and I’ve forwarded your feedback to the team. They’re currently discussing what would be necessary to change this behaviour since a lot of tooling depends on the existing setup.

georgeq · March 4, 2020, 3:19pm

That’s perfectly understandable. Thank you!

georgeq · March 9, 2020, 1:30pm

The message says “See console for more details”, but the console is completely empty.

On 2020.1.0a21 this could be solved by restarting Unity. On 2020.1.a024 you simply cannot solve it that way.

Bug Report:
Case 1226308

ROBYER1 · March 12, 2020, 8:25am

Same issue on 2020.1 beta, I’m sure many others will report this though

LeonhardP · March 13, 2020, 10:03pm

Thanks for the report. We will look into this.

tarahugger · April 10, 2020, 10:54pm

Same Issue here
Is there a workaround?

Edit: Workaround is to close Unity, delete your /Library/ folder, then restart.

Games4Stream · April 11, 2020, 2:00pm

Deleting the Library folder was necessary for me as well. Thanks for the tip.

kipperorrell8 · April 23, 2020, 9:49pm

Same issue here. currently sending the bug via the bug-reporter, I will try deleting the library folder after.
Unity 2020.2.0a7.826

kipperorrell8 · April 23, 2020, 10:06pm

Okay so deleting the library folder and reopening the project sorts the error out. I’m guessing a full reimport of all the library forces the engine to redownload the packages. It’s like the packages are licensed to users and the version of unity so they break when opening the newer version than when the packages were installed to the project.

LeonhardP · April 24, 2020, 11:00am

We were able to reproduce the issue on our side and the devs are investigating. You can check the latest status here: Unity Issue Tracker - You do not have entitlements for this package is thrown when package manager window is opened

tarahugger · April 24, 2020, 6:46pm

I just had this happen again, on a different project, and the scenario was:

project had a custom package in /packages/ that declared dependencies on Entities/Burst etc Therefore these packages only showed up in my package manager and project because of it. (they are not listed in my project’s manifest.json)
removed the custom package in explorer.
switched back to unity and it does the recompile thing.
realised that my project no longer has all the packages i need installed (Entities etc)
try to install the Entities package.
“you do not have the entitlements for this package”…

also, this had nothing to do with upgrades/downgrades as noted in the bug tracker link.

FallingRocketGames · May 16, 2020, 4:47am

just happened to me as well, all those packages were showing the same error, this happened after baking a scene with the universal render pipeline