Unity the Wrong Image Was Selected Please Try Again

Local folder or tarball paths

Troubleshooting

This section provides information on the following problems:

Blazon of fault: Fault message:
Full general startup issues - Mistake letters in the Package Manager window
- Packet Manager missing or window doesn't open
- Bug after upgrading Unity to new version
- Resetting your project's bundle configuration
Package installation issues - Bundle installation fails
- Packages not recognized
Problems installing git dependencies - No 'git' executable was found
- git-lfs: control not found
- Repository not institute
- Could not read Username: final prompts disabled
- Can't update Git version
Asset Store A growing library of free and commercial assets created by Unity and members of the customs. Offers a broad variety of assets, from textures, models and animations to whole project examples, tutorials and Editor extensions. More info
See in Glossary
packages (My Assets)
- 'Failed to parse Http response' in My Assets context
Scoped registries - Missing 'My Registries' in the Package Managing director window
Issues when edifice packages - Missing MonoBehaviour errors
- Loading error for hostfxr.dll on Windows

Yous can also run the Unity Parcel Director Diagnostics tool if you are experiencing problems that might be network-related. For more data, run into Network problems.

Mistake messages in the Package Manager window

The Bundle Manager displays mistake indicators in the Package Managing director window when information technology encounters problems.

System-wide issues

  • Network connection bug

    Error messages appear in the condition bar when the Packet Manager has detected an result that isn't related to a specific package. For example, if the Bundle Director can't access the package registry server, it displays this message in the condition bar:

    Network error message
    Network error bulletin
  • Mistake refreshing assets (or Error refreshing packages)

    If your network tin can't reach the bundle registry server, it'due south probably because there is a connection problem with the network. When you or your system administrator fix the network error, the status bar clears.

    If your network connection is working, but you aren't signed into your Unity account, the Parcel Managing director doesn't display any Nugget Store packages. When you try to apply the My Assets context, the Package Manager displays an error in the condition bar:

    Logged out of Unity account
    Logged out of Unity account

    Click the Sign in push button within the list view to sign into your Unity account through the Unity Hub.

Parcel-specific problems

  • If a specific parcel has a problem when loading or installing (for case, when determining which packet versions to load), the fault icon () appears in the package listing adjacent to the compromised package (A). To detect out what the problem is, open the compromised package'southward details view to see the detailed fault message (B):

    Dependency error message
    Dependency mistake message

Package Manager missing or window doesn't open

The Package Director window might get moved offscreen or hidden past another window. When this happens, it looks like the Packet Director window failed to open up. In this case, you can try to reset the window layout (Window > Layouts > Default) and reopen the Package Manager window again.

If the Package Director window still doesn't appear, check your Unity Console window A Unity Editor window that shows errors, warnings and other messages generated by Unity, or your own scripts. More info
Meet in Glossary
:

          Failed to resolve packages: The file [<projection-path>/Packages/manifest.json] is not valid JSON:   Unexpected token '}' at 44:1   }                  

This error message indicates that your manifest.json file is malformed. Information technology as well tells you the line number where the Package Manager failed to parse the file, and then y'all can prepare the JSON. In that location are a number of online validators that you can use to try to correct the trouble. Once y'all save the corrected file, Unity reloads the Bundle Managing director window.

If you upgraded from an early version of the Unity Editor, at that place may be other bug with your bundle manifest Each bundle has a manifest, which provides data nigh the package to the Package Manager. The manifest contains information such as the name of the bundle, its version, a description for users, dependencies on other packages (if any), and other details. More info
Run into in Glossary
file:

  • Equally of 2019.3, your manifest.json file should non comprise any references to the com.unity.bundle-manager-ui package. You lot can either reset your project's packet configuration or remove the post-obit line from the manifest's dependencies listing:

                                  "com.unity.bundle-managing director-ui": "2.1.ane",                          
  • Check to encounter if your project manifest Each Unity project has a project manifest, which acts equally an entry point for the Package Manager. This file must be available in the <project>/Packages directory. The Package Manager uses it to configure many things, including a listing of dependencies for that projection, besides as any package repository to query for packages. More info
    See in Glossary
    uses "exclude" equally a bundle version. This is an obsolete value for the dependenciesIn the context of the Package Manager, a dependency is a specific package version (expressed in the form package_name@package_version) that a projection or another package requires in order to work. Projects and packages employ the dependencies attribute in their manifests to define the prepare of packages they crave. For projects, these are considered direct dependencies; for packages, these are indirect, or transitive, dependencies. More info
    See in Glossary
    property. If you find any lines like these, remove the unabridged line. Package Managing director only installs packages that are explicitly included as a dependency in your project, then once you lot remove that entry, Bundle Manager ignores the package and doesn't install it.

If the Package Manager still fails to load, follow the procedures under Packages not recognized and Resetting your projection's package configuration.

Problems later upgrading Unity to new version

When you upgrade a project to a newer Unity version, the Package Director automatically updates incompatible packages to newer compatible versions. However, if your package doesn't compile, the Bundle Manager displays error letters in the Console.

To correct these letters, read the error messages and fix any problems you can. For instance, a packet might be missing a dependency on another bundle or version. In that case, yous tin can effort and install the package yourself.

You can also endeavour the post-obit sequence of solutions until you find something that works:

  • Support and then delete the Packages binder nether your project.
  • Dorsum upwardly and and then delete the package sources in your projection's Packages binder, leaving only the manifest.json file. Then try to reload the project.
  • Create a new empty project. If the Bundle Managing director window loads successfully, supplant the Library/PackageCache/com.unity.bundle-manager-ui@<version> folder in the failing project with the same folder from the newly created project.
  • As a last resort, yous can reset your project to the default packet Unity automatically pre-installs a select number of default packages (for example, the Analytics Library, Unity Timeline, etc.) when you create a new project. This differs from a bundled package considering y'all don't need to install it and it differs from a built-in package because it extends Unity'south features rather than existence able to enable or disable them.
    See in Glossary
    configuration and add back packages one at a time until it works.

Resetting your project'south package configuration

If a project has besides many package issues, you lot can reset your project dorsum to the default bundle configuration for the Editor's version of Unity. This operation resets all packages in your project. This might non fix the source of the trouble, merely information technology can help y'all effigy out what the problem is.

Note: You can't undo resetting your package configuration, so make sure yous back up the manifest.json file first or make sure your projection is under source control. You tin likewise take extra precautions by cloning your project and testing out the operation on the clone before proceeding.

To return to the default bundle configuration, select Reset Packages to defaults from the Assist menu.

Help > Reset Packages to defaults
Help > Reset Packages to defaults

Resetting a clone of your project

You tin as well test the return to the default packages before y'all perform the final alter:

  1. Clone your projection past copy-pasting your project binder and renaming it and so that it is easy to find (for case, if your projection is chosen MyProject so you could employ something similar clone_MyProject).

  2. Load your newly cloned project.

  3. From the Help carte du jour, select Reset Packages to defaults.

    Depending on the size of your project, this might take a few minutes.

  4. Bank check that it successfully reset the packages. If and then, you can perform the operation safely on the original projection.

Package installation fails

If you are trying to install a new packet from the registry and information technology is not working, it might be due to permission problems.

You must accept total permissions on the cache folder:

  • Windows: C:\Users\yourname\AppData\Local\Unity\enshroud
  • MacOS: ~/Users/Library/Unity/cache

Information technology might exist a trouble with the network. Check your firewall and proxy settings.

Sometimes institutional environments, such equally schools, regime offices, or network-protected workplaces fix up proxy servers to control traffic between the network and the Internet, and use their own server certificates which are non recognized by Unity or the Package Managing director. Talk to your network ambassador.

Packages not recognized

If you lot run into a lot of compilation errors, this might indicate that Unity is non recognizing the packages in your existing project. In this instance, you might exist missing a .NET component.

For Windows:

  1. Download and install Visual Studio 2017 version 15.nine.0 or higher with the .Internet Core cross-platform development workload selected under Other Toolsets.
  2. Download and install the .NET SDK v2.2.101 component.

For MacOS:

  1. Download and install the .Internet SDK v2.2.101 component.

  2. Install any recommended updates in Visual Studio

  3. Employ homebrew to brew and install mono:

                  brew update mash install mono # optional brew upgrade mono                          
  4. If necessary, delete the Library/obj/temp folder nether your project and restart Unity.

  5. If y'all are yet experiencing difficulties, endeavor rebooting your reckoner every bit well.

No 'git' executable was institute

If you attempt to install a package from a git URL, a message similar to this appears:

          Cannot perform upm functioning: Unable to add package [https://github.example.com/myuser/myrepository.git]: No 'git' executable was found. Delight install Git on your organization and restart Unity [NotFound] UnityEditor.EditorApplication:Internal_CallUpdateFunctions()                  

git-lfs: command non establish

If you are trying to download a bundle that uses Git LFS (Large File Storage), you might see this fault message:

          Error when executing git command. git-lfs filter-process: command not establish.                  

This indicates that Git LFS is probably non installed on your automobile. To make sure, you could test information technology on the command line:

          git lfs --version                  

If you lot see something like this, Git LFS is installed:

          git-lfs/2.8.0 (GitHub; darwin amd64; become one.12.seven)                  

Otherwise, you tin install it by post-obit the Bitbucket GitHub instructions.

Repository not found

If you specify a location that does not exist, a message similar to this 1 appears in the Unity Console:

          Cannot perform upm operation: Unable to add package [https://mycompany.github.com/gitproject/com.mycompany.mypackage.git]:   Error when executing git control. fatal: repository 'https://mycompany.github.com/gitproject/com.mycompany.mypackage.git/' non constitute  [NotFound] UnityEditor.EditorApplication:Internal_CallUpdateFunctions() (at /Users/builduser/buildslave/unity/build/Editor/Mono/EditorApplication.cs:310)                  

Check your spelling. To brand sure y'all are using the correct URL, go to the repository'due south folio and copy the URL from the Clone button:

Where to copy the URL on GitHub (A) and GitLab (B)
Where to copy the URL on GitHub (A) and GitLab (B)

Click the button to the right of the URL on GitHub (A) or GitLab (B) to re-create the URL to your clipboard.

If the location of the repository is correct, there may be another problem with the URL:

  • If you are targeting a specific revision, make sure your revision comes last. For case:
    https://github.instance.com/myuser/myrepository1.git#revision
  • If you are targeting a revision and the package is not at the root, brand sure the path query parameter precedes the revision anchor. For example:
    https://github.example.com/myuser/myrepository.git?path=/instance/binder#v1.2.three

Could non read Username: terminal prompts disabled

If you are trying to install a package from a private repository that requires hallmark, a message similar to this i appears in the Unity Console:

          Cannot perform upm performance: Unable to add bundle [https://mycompany.github.com/gitproject/com.mycompany.mypackage.git]:   Mistake when executing git control. fatal: could not read Username for 'https://mycompany.github.com': final 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 Bundle Manager does non provide an interactive terminal or dialog where you tin enter your username and countersign 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. Yet, the Package Director does not provide an interactive final or dialog where yous can enter your username and countersign for HTTP(Due south).

    To bypass this, use one of the workarounds suggested in Solutions for HTTPS.

  • SSH uses a pair of public and private SSH keys. You tin can add your public SSH key to Bitbucket, GitHub or GitLab and and then admission repositories without having to enter a username and password.

    However, if you have prepare a passphrase to keep your SSH key rubber, you yet have to enter that passphrase in a terminal or a dialog box in order to authorize your cardinal. In that case, you tin can utilise an SSH agent that can unlock your SSH key to cosign with the Parcel Manager on your behalf.

Solutions for HTTPS

The Packet Manager does not provide an interactive last or dialog where you tin can enter your HTTP(South) username and countersign. To bypass this, utilise ane of these workarounds:

  • Use a credential managing director (Git Credential Managing director for Windows or OSXKeyChain). Credential managers handle sending the password without having to use a last or a command prompt.
  • Utilise git-credentials from a terminal or command prompt. Then launch the Hub from the aforementioned terminal and then that Unity has access to the buried or stored credentials.
  • Apply SSH to authenticate instead. If you set upwardly your SSH key without a passphrase, the Parcel Manager doesn't have to decrypt it in order to authenticate with the Git server. If yous decide to use a passphrase for added security, you lot can even so get effectually the hallmark problem by using the ssh-agent on either macOS or Windows.

Solutions for SSH

If you lot are using the SSH protocol to install a package by Git URL, you might get an authentication mistake from Git. This typically happens when you prepare upwards a individual SSH key on your local machine that is protected by a passphrase.

The solution to this trouble is to set up an SSH agent that tin unlock your SSH primal to cosign with the Package Director on your behalf. Follow the instructions in the section that corresponds to your operating organization:

  • Setting upwards OpenSSH for Windows
  • Adding SSH keys to your SSH Amanuensis for macOS

Setting up OpenSSH for Windows

The native Windows OpenSSH version of the ssh-agent works ameliorate than the version bachelor past default with Git for Windows. This procedure explains how to ready the OpenSSH client and add together your central to its ssh-agent. If yous are using Git for Windows, y'all can also prioritize the native Windows OpenSSH over the Git for Windows SSH agent:

  1. Brand certain the OpenSSH Client is installed past searching for it in the Windows Settings Optional features window (Start > Settings, then search for "Optional features"). This applies to Windows 10+.

  2. Bank check your %PATH% environment variable to make sure the native Windows OpenSSH location appears (for instance, C:\WINDOWS\System32\OpenSSH\).

    Note: If y'all are already using Git for Windows, brand 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 amanuensis over the Git for Windows SSH amanuensis.

  3. In a PowerShell concluding, first the ssh-amanuensis process and brand sure it starts automatically:

                  # Ready the ssh-agent service to start automatically and manually start it now Get-Service ssh-agent | Prepare-Service -StartupType Automatic # Run the ssh-agent process to start the ssh-amanuensis service ssh-agent                          
  4. Import your key into the ssh-agent past running ssh-add on the command line so post-obit the instructions. By default, the amanuensis adds the %USERPROFILE%\.ssh\id_rsa key and prompts yous for the password.

                  # Import the central ssh-add                          

    To use a different key, you lot can specify it equally an argument:

                  # Ready the ssh-agent service to showtime automatically and manually start information technology at present ssh-add <your-secure-ssh-key-name>                          

    If you can't recollect the name of your key, you tin can inquire the agent to listing them:

                  ssh-add together -l                          
  5. 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", "$((Become-Command ssh).Source)", [Organisation.EnvironmentVariableTarget]::User)                          

Calculation SSH keys to your SSH Agent for macOS

Apply the ssh-add together command to add your SSH keys to the ssh-agent running on your macOS organization. The command parameter you use depends on your version of macOS:

  • Prior to macOS 12, use:

                  ssh-add -K ~/.ssh/<your-secure-ssh-key-name>                          
  • Starting with macOS 12, utilise:

                  ssh-add --apple-use-keychain ~/.ssh/<your-secure-ssh-fundamental-name>                          

After you run this control, the concluding asks for the password to unlock your SSH primal and then adds it to the macOS keychain. However, once you lot 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 1 if you don't observe it), and add the following:

          Host *     UseKeychain yes     AddKeysToAgent yes     IdentityFile ~/.ssh/<your-secure-ssh-key-name>                  

Restart your car to utilize these changes.

Can't update Git version

If you are trying to update your Git dependency The Package Managing director retrieves Git dependencies from a Git repository directly rather than from a packet registry. Git dependencies use a Git URL reference instead of a version, and there's no guarantee about the package quality, stability, validity, or even whether the version stated in its package.json file respects Semantic Versioning rules with regards to officially published releases of this package. More than info
See in Glossary
to a newer version from the repository, merely it's not working, information technology'due south probably considering your Git dependency is locked. If you desire to update your Git dependency to a newer version from the repository, use the Add package from git URL push button and enter a Git URL. For more information, encounter Locked Git dependencies.

'Failed to parse Http response' in My Assets context

If you encounter the post-obit message in the Console window when trying to download an Asset Store package, at that place might be a trouble 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 Shop packet directory and then try downloading the assets again.

Alert: If your project contains a lot of asset data, this might have a lot of fourth dimension and bandwidth to re-download everything.

Missing 'My Registries' in the Packet Manager window

Non all registry providers are compatible with Unity's Package Director. If the package registry server you added does not implement the /-/v1/search or /-/all endpoints, your scoped registry is not compatible with Unity's Package Managing director, and doesn't appear in the My Registries context in the Packet Manager window.

Missing MonoBehaviour errors

While building, if there are a lot of errors nigh Missing Beliefs, 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 case, if yous have a prefab An asset type that allows you to store a GameObject complete with components and properties. The prefab acts as a template from which you can create new object instances in the scene. More info
See in Glossary
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, yous can either lower the stripping level for the UnityLinker or declare the parcel's assemblies inside the link.xml file in order to preserve them from being stripped:

          <linker>     <assembly fullname="Unity.2D.SpriteShape.Runtime" preserve="all"/>     <associates fullname="Unity.second.Common.Runtime" preserve="all"/>  </linker>                  

For more than data on stripping levels and the UnityLinker, see Managed code stripping.

Loading error for hostfxr.dll on Windows

If the Panel reports that the hostfxr.dll library was found, but Unity failed to load it from C:\<path_to_app>\hostfxr.dll, yous can fix this error on Windows 7 or Windows Server 2008 R2 by installing both KB2999226 and KB2533623 patches.

Local folder or tarball paths

millarnerty1951.blogspot.com

Source: https://docs.unity3d.com/Manual/upm-errors.html

0 Response to "Unity the Wrong Image Was Selected Please Try Again"

Post a Comment

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel