Failed to import package with error cannot import package in play mode что делать

«Couldn’t decompress package» error when importing #157

I have cloned and successfully built HoloToolkit-Unity. However, when I try to do Assets -> Import Package -> Custom Package… I get the following error:

Failed to import package with error: Couldn’t decompress package

I’ve rebuilt it twice. I’ve also tried moving it to various places on my hard disk with no luck. Any ideas whats up? Here’s a link to the package file it produced.

The text was updated successfully, but these errors were encountered:

@anandx how did you create your unity package?

I just tried the following and it worked:

1. Opened the cloned HoloToolkit-Unity in Unity
2. Right click on Assets > Export package
3. Give it a name and export
4. Used a different Test project
5. Right click on Assets > Import Package > Custom Package
6. Selected the previously created package > Open
7. Clicked Import in the Import dialog box.
8. Everything worked.

I suspect something was created incorrectly in your unity package.

Hmm. I am using those exact steps but at step 6 I get the compression
error. I have retried this process 3x including fresh clone from git.

Might be a broader Unity related error? I’m fairly new to Unity, wonder if
anyone has suggestions of what to try?

On Thu, Aug 4, 2016 at 6:34 PM Neeraj Wadhwa notifications@github.com
wrote:

I just tried the following and it worked:

1. Opened the cloned HoloToolkit-Unity in Unity
2. Right click on Assets > Export package
3. Give it a name and export
4. Used a different Test project
5. Right click on Assets > Import Package > Custom Package
6. Selected the previously created package > Open
7. Clicked Import in the Import dialog box.
8. Everything worked.

I suspect something was created incorrectly in your unity package.

Источник

Unity: Failed to import package with error: Couldn’t decompress package #2

What happened?

Where I got the package file and key?

I send request to https://kharma.unity3d.com/api/en-US/content/download/ .json to fetch the package file’s download URL and decryption key. Here is an example of the response:

How I decrypt the file?

I basically copy paste the test code from here.

How I import the output file into Unity?

What’s the expected result?

Should be able to import decrypted package file into Unity successfully.

The text was updated successfully, but these errors were encountered:

Hey @moscartong — looks like something changed in the crypto module — i see a similar failure with the test suite when running with modern node ( 8.2.1 ) but it works if i revert to old node ( 6.7.0 ) — i’ll isolate the change and work on a fix!

Huge thank you for finding this issue, and communicating it so clearly with the above description! 🚀 💯

still investigating — but it looks like the behavior of Decipher.final is differing by node version.

C:Usersbengitunity-package-decrypt (master) (unity-package-decrypt@0.1.0)
λ npm test

unity-package-decrypt@0.1.0 test C:Usersbengitunity-package-decrypt
mocha

UnityDecryptClient
√ should construct
√ should createDecryptStream
3291616
3291600
3103469
1) should decrypt

2 passing (64ms)
1 failing

UnityDecryptClient should decrypt:

AssertionError [ERR_ASSERTION]: 3103469 == 3171523

at client.decrypt.then (e:vs_workspaceunity-package-decrypttestbasic.js:34:24)
at
at process._tickCallback (internal/process/next_tick.js:188:7)

npm ERR! Test failed. See above for more details.

C:Usersbengitunity-package-decrypt (master) (unity-package-decrypt@0.1.0)
λ nvm use 6.7.0
Now using node v6.7.0 (64-bit)

C:Usersbengitunity-package-decrypt (master) (unity-package-decrypt@0.1.0)
λ npm test

unity-package-decrypt@0.1.0 test C:Usersbengitunity-package-decrypt
mocha

UnityDecryptClient
√ should construct
√ should createDecryptStream
3291616
3291600
3171523
√ should decrypt (62ms)

Источник

Troubleshooting

This section provides information on the following issues:

You can also run the Unity Package Manager Diagnostics tool if you are experiencing problems that might be network-related. For more information, see Diagnose network issues.

Error messages in the Package Manager window

The Package Manager displays error indicators in the Package Manager window when it encounters problems.

System-wide issues

Network connection issues

Error messages appear in the status bar when the Package Manager has detected an issue that isn’t related to a specific package. For example, if the Package Manager can’t access the package registry server, it displays this message in the status bar:

Network error message

Error refreshing assets (or Error refreshing packages)

If your network can’t reach the package registry server, it’s probably because there is a connection problem with the network. When you or your system administrator diagnose and fix the network error, the status bar clears.

If your network connection is working, but you aren’t 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:

Logged out of Unity account

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

Package-specific issues

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):

Dependency error message

Package Manager missing or window doesn’t open

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 A Unity Editor window that shows errors, warnings and other messages generated by Unity, or your own scripts. More info
See in Glossary :

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 Each package has a manifest, which provides information about the package to the Package Manager. The manifest contains information such as the name of the package, its version, a description for users, dependencies on other packages (if any), and other details. More info
See in Glossary 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 Each Unity project has a project manifest, which acts as an entry point for the Package Manager. This file must be available in the

/Packages directory. The Package Manager uses it to configure many things, including a list of dependencies for that project, as well as any package repository to query for packages. More info
See in Glossary 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.

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

Problems after upgrading Unity to new version

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.

To correct these messages, read the error messages and fix any problems you can. For example, a package might be missing a dependency on another package or version. In that case, you can try and install the package yourself.

You can also try the following sequence of solutions until you find something that works:

• Back up and then delete the Packages folder under your project.
• Back up and then delete the package sources in your project’s Packages folder, leaving only the manifest.json file. Then try to reload the project.
• Create a new empty project. If the Package Manager window loads successfully, replace the Library/PackageCache/com.unity.package-manager-ui@ folder in the failing project with the same folder from the newly created project.
• As a last resort, you can reset your project to the default package 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 because you don’t need to install it and it differs from a built-in package because it extends Unity’s features rather than being able to enable or disable them.
  See in Glossary configuration and add back packages one at a time until it works.

Resetting your project’s package configuration

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.

To return to the default package configuration, select Reset Packages to defaults from the Help menu.

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

Resetting a clone of your project

You can also test the return to the default packages before you perform the final change:

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 clone_MyProject ).

Load your newly cloned project.

From the Help menu, select 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.

Package installation fails

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

You must have full permissions on the cache folder:

• Windows: C:UsersyournameAppDataLocalUnitycache
• macOS:

It might be a problem with the network. Check your firewall and proxy settings.

Sometimes institutional environments, such as schools, government offices, or network-protected workplaces set up proxy servers to control traffic between the network and the Internet, and use their own server certificates which are not recognized by Unity or the Package Manager. Talk to your network administrator.

Packages not recognized

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.

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

Download and install the .NET SDK v2.2.101 component.

Install any recommended updates in Visual Studio

Use homebrew to brew and install mono:

If necessary, delete the Library/obj/temp folder under your project and restart Unity.

If you are still experiencing difficulties, try rebooting your computer as well.

Unable to add package from Git URL

Insufficient drive space

If your installation drive is out of space or low on space, consider changing the location of the package caches:

Package version has no signature

This message can appear when you fetch a Unity package from a scoped registry. Unity signs packages that it creates, except for older packages, which aren’t necessarily re-signed in later releases. If you copy an unsigned Unity package from a scoped registry to another registry, Package Manager can’t determine if the package content is safe and identical to the original package.

If you encounter this message, try these solutions:

• Use another version of the package.
• Fetch the Unity package from the Unity Registry.
• If you own the scoped registry, make sure you copy the newest version of the package from the Unity Registry.

Package version doesn’t have a valid signature

Packages have a signature to ensure that the content wasn’t changed before or during transit. An invalid signature typically occurs in the following situations:

• Someone published the package with modifications on their own registry.
• An error occurred while transferring the file to the end user.

In both cases, Package Manager considers the package to be potentially malicious.

When you encounter an invalid signature, you can try to install a different version of the package. You should also avoid using Unity packages from a registry other than the Unity Registry.

If you are sharing a Unity package that contains a fix, consider using a Git URL or embedding the package in your project.

No ‘git’ executable was found

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

git-lfs: command not found

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

This indicates that Git LFS is probably not installed on your machine. To make sure, you could test it on the command line:

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

Otherwise, you can install it by following the Bitbucket GitHub instructions.

Repository not found

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

Check your spelling. To make sure you are using the correct URL, go to the repository’s page and copy the URL from the Clone button:

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 copy 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 example:
  https://github.example.com/myuser/myrepository1.git#revision
• If you are targeting a revision and the package is not at the root, make sure the path query parameter precedes the revision anchor. For example:
  https://github.example.com/myuser/myrepository.git?path=/example/folder#v1.2.3

Could not read Username: terminal prompts disabled

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

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.

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

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.

Solutions for HTTPS

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:

• Use a credential manager (Git Credential Manager for Windows or OSXKeyChain). Credential managers handle sending the password without having to use a terminal or a command prompt.
• Use git-credentials from a terminal or command prompt, then launch the Hub from the same terminal so that Unity has access to the cached or stored credentials.
• Use SSH to authenticate instead. If you set up your SSH key without a passphrase, the Package Manager doesn’t have to decrypt it to authenticate with the Git server. If you decide to use a passphrase for added security, you can use the ssh-agent on either macOS or Windows to get around the authentication problem.

Solutions for SSH

If you use 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:

Setting up OpenSSH for Windows

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. To do this, search for it in the Windows Settings Optional features window (Start > Settings, then search for “Optional features”). This applies to Windows 10+.

Check your %PATH% environment variable to make sure the native Windows OpenSSH location appears (for example, C:WINDOWSSystem32OpenSSH ).

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:

Import your key into the ssh-agent. To do this, run ssh-add on the command line and then follow the instructions. By default, the agent adds the %USERPROFILE%.sshid_rsa key and prompts you for the password.

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

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:

Adding SSH keys to your SSH Agent for macOS

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

Prior to macOS 12, use:

Starting with macOS 12, use:

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 make sure you don’t need to re-enter your password after you restart your system, open the

/.ssh/config file (or create one if you don’t find it), and add the following:

Restart your machine to apply these changes.

Can’t update Git version

If you are trying to update your Git dependency The Package Manager retrieves Git dependencies from a Git repository directly rather than from a package 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 info
See in Glossary 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.

‘Failed to parse Http response’ in My Assets context

If you see the following message in the Console window when you try to download an Asset Store package, there might be a problem with your Asset Store cache:

[PackageManager] Error Failed to parse response. UnityEditor.AsyncHTTPClientone(State, Int32)

To solve this problem, delete all downloaded assets from the Asset Store package directory and then try to download the assets again.

Warning: If your project contains a lot of asset data, it might take a lot of time and bandwidth to re-download everything.

Missing ‘My Registries’ in the Package Manager window

Not all registry providers are compatible with Unity’s Package Manager. 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 Manager, and doesn’t appear in the My Registries context in the Package Manager window.

Missing MonoBehaviour errors

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 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, 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:

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

Источник

Вернуться в Почемучка

Кто сейчас на конференции

Сейчас этот форум просматривают: нет зарегистрированных пользователей и гости: 23