이 섹션은 다음 문제에 관한 정보를 제공합니다.
|Type of error:||Error message:|
|General startup issues||- Error messages in the Package Manager window
- Package Manager missing or window doesn’t open
- Problems after upgrading Unity to new version
- Resetting your project’s package configuration
|Package installation issues||- Package installation fails
- Packages not recognized
|Problems installing git dependencies||- No ‘git’ executable was found
- git-lfs: command not found
- Repository not found
- Could not read Username: terminal prompts disabled
- Can’t update Git version
|Asset Store packages (My Assets)||- ‘Failed to parse Http response’ in My Assets context|
|Scoped registries||- Missing ‘My Registries’ in the Package Manager window|
|Issues when building packages||- Missing MonoBehaviour errors
- Loading error for hostfxr.dll on Windows
네트워크 관련 문제가 발생한 경우 Unity 패키지 관리자 진단 툴을 실행할 수도 있습니다. 자세한 내용은 네트워크 문제를 참조하십시오.
패키지 관리자는 문제가 발생하면 Package Manager 창에 오류 표시기를 표시합니다.
시스템 관련 문제
Error messages that appear in the status bar indicate the Package Manager has detected an issue that is not related to a specific package. For example, if the Package Manager cannot access the package registry server, it displays this message in the status bar:
네트워크가 패키지 레지스트리 서버에 도달하지 못하는 경우 네트워크에 연결 문제가 발생했기 때문일 수 있습니다. 여러분 또는 시스템 관리자가 네트워크 오류를 수정하면 상태 표시줄의 내용이 지워집니다.
If your network connection is working, but you are not signed into your Unity account, the Package Manager doesn’t display any Asset Store packages. When you try to use the My Assets context, the Package Manager displays an error in the status bar:
If a specific package has a problem when loading or installing (for example, when determining which package versions to load), the error icon () appears in the package list next to the compromised package (A). To find out what the problem is, open the compromised package’s details view to see the detailed error message (B):
While building, if there are a lot of errors about Missing Behavior, the UnityLinker might be mistakenly stripping out a component that it thinks is unreferenced. It often does this because the stripping level is too aggressive. For example, if you have a prefab in an AssetBundle that references the SpriteShape component in the 2D SpriteShape package, the object might be missing and might generate compiler warnings.
To fix this, you can either lower the stripping level for the UnityLinker or declare the package’s assemblies inside the
link.xml file in order to preserve them from being stripped:
<linker> <assembly fullname="Unity.2D.SpriteShape.Runtime" preserve="all"/> <assembly fullname="Unity.2D.Common.Runtime" preserve="all"/> </linker>
For more information on stripping levels and the UnityLinker, see Managed code stripping.
The Package Manager window might get moved offscreen or hidden by another window. When this happens, it looks like the Package Manager window failed to open. In this case, you can try to reset the window layout (Window > Layouts > Default) and reopen the Package Manager window again.
If the Package Manager window still doesn’t appear, check your Unity Console window:
패키지를 확인하지 못함: [<project-path>/Packages/manifest.json] 파일이 유효한 JSON이 아님: 44:1에서 예기치 못한 토큰 '}' }
This error message indicates that your
manifest.json file is malformed. It also tells you the line number where the Package Manager failed to parse the file, so you can fix the JSON. There are a number of online validators that you can use to try to correct the problem. Once you save the corrected file, Unity reloads the Package Manager window.
If you upgraded from an early version of the Unity Editor, there may be other problems with your package manifest file:
As of 2019.3, your
manifest.json file should not contain any references to the com.unity.package-manager-ui package. You can either reset your project’s package configuration or remove the following line from the manifest’s dependencies list:
Check to see if your project manifest uses “exclude” as a package version. This is an obsolete value for the dependencies property. If you find any lines like these, remove the entire line. Package Manager only installs packages that are explicitly included as a dependency in your project, so once you remove that entry, Package Manager ignores the package and doesn’t install it.
When you upgrade a project to a newer Unity version, the Package Manager automatically updates incompatible packages to newer compatible versions. However, if your package doesn’t compile, the Package Manager displays error messages in the Console.
이러한 메시지를 해결하려면 오류 메시지를 읽은 후 해결할 수 있는 문제를 수정해야 합니다. 예를 들어 패키지에 다른 패키지나 버전에 대한 종속성이 없는 경우 패키지를 직접 설치할 수 있습니다.
또한 제대로 동작할 때까지 다음과 같은 해결책을 순서대로 시도해 볼 수 있습니다.
Packagesfolder under your project.
Packagesfolder, leaving only the
manifest.jsonfile. Then try to reload the project.
Library/PackageCache/com.unity.package-manager-ui@<version>folder in the failing project with the same folder from the newly created project.
레지스트리에서 새 패키지를 설치할 수 없는 경우에는 권한 관련 문제일 수 있습니다.
다음의 캐시 폴더에 대한 전체 권한이 있어야 합니다.
때때로 학교, 관공서 같은 기관이나 네트워크 보호 작업 공간에서는 프록시 서버를 설치하여 네트워크와 인터넷 간 트래픽을 제어하고, Unity 또는 패키지 관리자에서 인식되지 않는 고유한 서버 인증서를 사용하십시오. 자세한 내용은 네트워크 관리자에 문의하시기 바랍니다.
If you see a lot of compilation errors, this might indicate that Unity is not recognizing the packages in your existing project. In this case, you might be missing a .NET component.
.NET SDK v2.2.101 컴포넌트를 다운로드하여 설치합니다.
Visual Studio의 권장 업데이트를 설치합니다.
Homebrew를 사용하여 mono를 브루잉(brew)하고 설치합니다.
brew update brew install mono # optional brew upgrade mono
If necessary, delete the
Library/obj/temp folder under your project and restart Unity.
여전히 문제가 발생하면 컴퓨터를 재부팅합니다.
If a project has too many package issues, you can reset your project back to the default package configuration for the Editor’s version of Unity. This operation resets all packages in your project. This might not fix the source of the problem, but it can help you figure out what the problem is.
Note: You can’t undo resetting your package configuration, so make sure you back up the
manifest.json file first or make sure your project is under source control. You can also take extra precautions by cloning your project and testing out the operation on the clone before proceeding.
기본 패키지 설정으로 되돌아가려면 Help 메뉴에서 Reset Packages to defaults를 선택하십시오.
최종 변경 사항을 적용하기 전에 다음 단계에 따라 패기지 초기화를 테스트해볼 수도 있습니다.
Clone your project by copy-pasting your project folder and renaming it so that it is easy to find (for example, if your project is called
MyProject then you could use something like
Load your newly cloned project.
도움말 메뉴에서 Reset Packages to defaults를 선택합니다.
Depending on the size of your project, this might take a few minutes.
Check that it successfully reset the packages. If so, you can perform the operation safely on the original project.
If you try to install a package from a git URL, a message similar to this appears:
Cannot perform upm operation: Unable to add package [https://github.example.com/myuser/myrepository.git]: No 'git' executable was found. Please install Git on your system and restart Unity [NotFound] UnityEditor.EditorApplication:Internal_CallUpdateFunctions()
If you are trying to download a package that uses Git LFS (Large File Storage), you might see this error message:
Error when executing git command. git-lfs filter-process: command not found.
This indicates that Git LFS is probably not installed on your machine. To make sure, you could test it on the command line:
git lfs --version
If you see something like this, Git LFS is installed:
git-lfs/2.8.0 (GitHub; darwin amd64; go 1.12.7)
존재하지 않는 위치를 지정하면 다음과 유사한 메시지가 Unity 콘솔에 나타납니다.
Cannot perform upm operation: Unable to add package [https://mycompany.github.com/gitproject/com.mycompany.mypackage.git]: Error when executing git command. fatal: repository 'https://mycompany.github.com/gitproject/com.mycompany.mypackage.git/' not found [NotFound] UnityEditor.EditorApplication:Internal_CallUpdateFunctions() (at /Users/builduser/buildslave/unity/build/Editor/Mono/EditorApplication.cs:310)
철자를 확인하십시오. 정확한 URL을 사용하려면 저장소의 페이지로 이동한 후 Clone 버튼으로 URL을 복사하십시오.
GitHub (A) 또는 GitLab (B)에서 URL 오른쪽에 있는 버튼을 클릭하면 URL을 클립보드에 복사합니다.
If the location of the repository is correct, there may be another problem with the URL:
pathquery parameter precedes the revision anchor. For example:
인증이 필요한 프라이빗 저장소에서 패키지를 설치하려고 하면 다음과 유사한 메시지가 Unity 콘솔에 나타납니다.
Cannot perform upm operation: Unable to add package [https://mycompany.github.com/gitproject/com.mycompany.mypackage.git]: Error when executing git command. fatal: could not read Username for 'https://mycompany.github.com': terminal prompts disabled [NotFound] UnityEditor.EditorApplication:Internal_CallUpdateFunctions() (at /Users/builduser/buildslave/unity/build/Editor/Mono/EditorApplication.cs:310)
This message is likely due to the fact that Package Manager does not provide an interactive terminal or dialog where you can enter your username and password for HTTP, or your passphrase to unlock your SSH key:
With HTTP(S), every time you log onto BitBucket, GitHub or GitLab you need to enter your username and password in a terminal or a dialog box. However, the Package Manager does not provide an interactive terminal or dialog where you can enter your username and password for HTTP(S).
To bypass this, use one of the workarounds suggested in Solutions for HTTPS.
However, if you have set up a passphrase to keep your SSH key safe, you still have to enter that passphrase in a terminal or a dialog box in order to authorize your key. In that case, you can use an SSH agent that can unlock your SSH key to authenticate with the Package Manager on your behalf.
The Package Manager does not provide an interactive terminal or dialog where you can enter your HTTP(S) username and password. To bypass this, use one of these workarounds:
If you are using the SSH protocol to install a package by Git URL, you might get an authentication error from Git. This typically happens when you set up a private SSH key on your local machine that is protected by a passphrase.
The solution to this problem is to set up an SSH agent that can unlock your SSH key to authenticate with the Package Manager on your behalf. Follow the instructions in the section that corresponds to your operating system:
The native Windows OpenSSH version of the ssh-agent works better than the version available by default with Git for Windows. This procedure explains how to set up the OpenSSH client and add your key to its ssh-agent. If you are using Git for Windows, you can also prioritize the native Windows OpenSSH over the Git for Windows SSH agent:
Make sure the OpenSSH Client is installed by searching for it in the Windows Settings Optional features window (Start > Settings, then search for “Optional features”). This applies to Windows 10+.
%PATH% environment variable to make sure the native Windows OpenSSH location appears (for example,
Note: If you are already using Git for Windows, make sure the native Windows OpenSSH location appears before the Git for Windows SSH location in your
%PATH% variable. This ensures that Windows uses the native Windows OpenSSH agent over the Git for Windows SSH agent.
In a PowerShell terminal, start the
ssh-agent process and make sure it starts automatically:
# Set the ssh-agent service to start automatically and manually start it now Get-Service ssh-agent | Set-Service -StartupType Automatic # Run the ssh-agent process to start the ssh-agent service ssh-agent
Import your key into the ssh-agent by running
ssh-add on the command line and then following the instructions. By default, the agent adds the
%USERPROFILE%\.ssh\id_rsa key and prompts you for the password.
# Import the key ssh-add
To use a different key, you can specify it as an argument:
# Set the ssh-agent service to start automatically and manually start it now ssh-add <your-secure-ssh-key-name>
If you can’t remember the name of your key, you can ask the agent to list them:
If you installed Git for Windows, reset the
%GIT-SSH% environment variable to make sure that Git always uses the native Windows OpenSSH version of the ssh-agent:
[Environment]::SetEnvironmentVariable("GIT_SSH", "$((Get-Command ssh).Source)", [System.EnvironmentVariableTarget]::User)
Use the following command to add your SSH keys to the ssh-agent running on your macOS system:
ssh-add -K ~/.ssh/<your-secure-ssh-key-name>
After you run this command, the terminal asks for the password to unlock your SSH key and then adds it to the macOS keychain. However, once you restart your system, every key stored in the ssh-agent is reset.
To prevent re-entering your password after restarting your system, open the
~/.ssh/config file (or create one if you don’t find it), and add the following:
Host * UseKeychain yes AddKeysToAgent yes IdentityFile ~/.ssh/<your-secure-ssh-key-name>
Restart your machine to apply these changes.
If you are trying to update your Git dependency to a newer version from the repository, but it’s not working, it’s probably because your Git dependency is locked. If you want to update your Git dependency to a newer version from the repository, use the Add package from git URL button and enter a Git URL. For more information, see Locked Git dependencies.
Not all registry providers are compatible with Unity’s Package Manager. If the package registry server you added does not implement the
/-/all endpoints, your scoped registry is not compatible with Unity’s Package Manager, and doesn’t appear in the My Registries context in the Package Manager window.
If you see the following message in the Console window when trying to download an Asset Store package, there might be a problem with your Asset Store cache:
[PackageManager] Error Failed to parse response. UnityEditor.AsyncHTTPClient![:D](https://forum.unity.com/styles/default/xenforo/clear.png)one(State, Int32)
To solve this problem, delete all downloaded assets from the Asset Store package directory and then try downloading the assets again.
Warning: If your project contains a lot of asset data, this might take a lot of time and bandwidth to re-download everything.