Error while importing package: Couldn't set permissions

Unity Engine
1

I just installed Unity (free) and when I import a package I have this error: “Error while importing package: Could not set permissions”

2

I have the same problem. In my case, ~/Library/Logs/Unity/Editor.log reads:

Initialize mono
2009-11-01 20:59:44.215 Unity[2728:20b] NSDocumentController Info.plist warning: The values of CFBundleTypeRole entries must be ‘Editor’, ‘Viewer’, ‘None’, or ‘Shell’.
projectPath.empty()

(Filename: /Users/build/builds/unity-26/unity-2.6.x/Projects/../Editor/Src/ProjectWizardUtility.cpp Line: 184)

path.empty () || path[0] != kPathNameSeparator

(Filename: /Users/build/builds/unity-26/unity-2.6.x/Projects/../Editor/Platform/OSX/EditorUtility.mm Line: 421)

Usage:
verify_permissions [–is-unity-project] [–fix-permissions] [–uid=USER_ID] PROJECT_PATH [PROJECT_PATH2 […]]
’ is not a valid directory path
’
Usage:
verify_permissions [–is-unity-project] [–fix-permissions] [–uid=USER_ID] PROJECT_PATH [PROJECT_PATH2 […]]

*Authorized fix permissions failed

Couldn’t change permissions

(Filename: /Users/build/builds/unity-26/unity-2.6.x/Projects/../Editor/Src/Argv.cpp Line: 80)

3

I extracted verify_permissions from the Unity app package and ran it on the command-line. I did the following:

karanvasudeva$ ./verify_permissions /Applications/Unity/
verify_permissions /Applications/Unity/, running for karanvasudeva
Done verifying - no errors

karanvasudeva$ ./verify_permissions /Users/Shared/Unity/Island\ Demo/
verify_permissions /Users/Shared/Unity/Island Demo/, running for karanvasudeva
Done verifying - no errors

karanvasudeva$ ./verify_permissions /Users/Shared/
verify_permissions /Users/Shared/, running for karanvasudeva

  • /Users/Shared/.localized (uid=root, perms=0644) is not writeable by karanvasudeva. Permissions need fixing

karanvasudeva$ sudo find /Users/Shared/ ! -perm -777 -exec chmod 777 {} ;
karanvasudeva$ ./verify_permissions /Users/Shared/
verify_permissions /Users/Shared/, running for karanvasudeva
Done verifying - no errors

And I’ve still got the same problem, no matter what package I open.

4

OK, on the basis of heavy trawling of the support forums, I’m guessing that this might be happening because I’m running on a case-sensitive filesystem (on a MacBook).

If this is indeed the problem, as I will intend to verify by reformatting, it really needs to go in the Support FAQ.

I should add that I’d been running Unity Indie 2.5.1 perfectly well until recently on a case-insensitive filesystem.

5

Yep. I’ve seen other people say they get an error message if they try running Unity on a case-sensitive file system.

–Eric

6

Confirmed. Thanks, Eric. I’ll send a note to support@unity3d.com and ref this.

7

Another thing to try here… what happens if you take the space out of the filename (ie, change it to “IslandDemo”)?

@jngl: what was the name of the package you tried to import? Did it have a space or other non-alphanumeric character in it somewhere?

I think the internal launching of verify_permissions might be failing to escape the space in the pathname, which would make the shell treat it as two invalid pathname parameters. Just a guess…

8

Hi.

Im running last version of Unity Free on Windows 7 and i have this same problem. What i do?

9

Hi,
I’v resolved this problem by changing a project path. By default the Unity create your project inside a language specific folder for ex. C:\Documents and Settings\user\Мои документы\New Unity Project 1. So just create a new project on another location (for ex.: c:\MyUnityProjects).

10

Hi.

My project path is alright, but I have that problem too…

That’s alright at home, but I can’t import anything at school. That very troublesome…

(Sorry for my English, that’s not my first language…)

11

I guess there are no news regarding this problem?
Today I found out that I have the same issue (on a Vista laptop). I can’t import any packages, not the standard assets or the FPS tutorial-assets.

I tried changing the project path (to c:\MyUnityProject) but it did not help.
As of now I have no idea how to solve this and I would really need these packages.

Edit: When I tried starting a completely new project and set the path to C:.… it suddenly worked.
So, as some people have already said that seems to be the solution for now.

12

Hi.
This solution helped me. Thanks :slight_smile:

13

I think it could be the long of the path. So the problem is fixed when you use a shorter path.

14

I knew that searching the forums would get me a sollution to that problem :slight_smile:

(belated) Thanks Hiker

15

I’v changed the project path but it was still not working. I shorted it and worked.
So, I think the long of the path is the problem too…

16

This is still an issue in 2019.2.1.