Project import errors

Why did my project fail to import?

If a project fails to import you may see an error, please check below for each one and why you may be seeing it:

NPM & Yarn

Failed to parse package.json or package-lock.json as valid JSON

Failed to parse package.json or yarn.lock as valid JSON

Please check the package.json & lockfile is valid JSON, any manual manipulation of these files may result in a missing/extra character where it is not expected. Use any of the online tools to validate it is correct JSON. To test locally: `npm install` should pass without errors.

General

Failed to process manifest FILE_NAME

Where possible we try to show as much info as we have, but processing files and extracting dependencies is a complex process and sometimes things can go wrong. If you received this error please contact support@snyk.io so we can look into it further.

The manifest file is missing, has been moved or renamed. If this is intentional, please deactivate or delete this project in settings.

You may receive a missing manifest error if you have deleted, moved or renamed the manifest file which Snyk read during the initial project import.

To resolve this issue you need to restore the manifest file to same location as it was at during the initial project import. Or if the move was intentional, then deactivate or delete the Snyk project and re-import the project again.

RubyGems

Failed to process RubyGems lockfile contents

We were unable to process the Gemfile.lock to extract dependencies from it. Please contact support on support@snyk.io and if possible share the lockfile you used so we can identify the issue.

Bitbucket

If you are manually adding a project to Snyk by using the `Add custom file location` you need to ensure the folder path and file name are in the correct case that matches your repo. For example if you have on BBS myproject/MyRepo and inside this a subfolder like GoofFolder which contains goof code with manifest files etc, adding manually gooffolder/package.json will fail, adding manually GoofFolder/package.json will work.

.Net

Satisfying version not found for cousin dependencies

When importing a .Net project, Snyk is creating the dependency tree according to the.*proj file. According to the NuGet logic, it is not allowed to use the same package with different versions in the same project. For example, let's assume that Package A and Package B are direct dependencies of the same project and both use Package C, meaning Package C is a transitive dependency. When resolving the version of Package C, it must be resolved into 1 version and to satisfy the requirements of Package A and Package B. Failing to do that will result in the error "Satisfying version not found for cousin dependencies error".

To troubleshoot the issue, please try to build the project. If it was built successfully, please reach out to support@snyk.io and we will look into it. If it wasn't, please make sure that all of the dependencies you are using in your project are not conflicting.

Satisfying version not found

When importing a .Net project, Snyk is creating the dependency tree according to the packages.config or .*proj files. In order to be able to resolve the version of all dependencies, they should be compatible with the target framework of the project. In case one or more of the dependencies are not compatible, we will return the "Satisfying version not found" error.

Target framework not present in <project_FileName>

In order to be able to build a dependency tree, Snyk needs to be able to determine what is the target framework of the project. Currently, we require the target framework to be part of the .*proj file. Support for using props file will be coming soon.

Articles in this section