Project import errors

Why did my project fail to import?

While importing a project into the Snyk console, you may sometimes encounter an error for a variety of reasons. We do our best to give you some guidance with the error text such as follows:

Screen_Shot_2019-09-26_at_2.07.00_PM.jpg

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.

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.

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.

Infrastructure as Code (Kubernetes / Helm)

Failed to download Helm chart file

This error is probably caused by a failure to download the Chart.yaml file from your git repository. This might mean Snyk does not have the correct permissions to access the file or that it has been deleted.

If you are using a Snyk broker, make sure you follow the relevant configuration instructions.

Failed to find a proper values file

Snyk needs the values.yaml file to render the template. This file needs to be in the same folder as the Charts.yaml file.

Failed to receive the content of the templates folder Failed to get the file: <FileName> in order to template the chart

Please make sure that there is a templates folder in the same directory as the Chart.yaml file. This folder should contain templates and helper files (*.tpl) that we access as part of the import flow. For more details about the expected format of Helm Charts, please see the Scan and fix security issues in your Helm Charts.

If you are using a Snyk broker, make sure you follow the relevant configuration instructions

Failed to run Helm template using the chart

You can check whether your chart is valid by testing locally by running helm template, which should pass without errors.

Note that we don’t yet support Helm charts which use an internal Helm repository to fetch dependencies or that require additional values files to render the Chart.

Infrastructure as Code (Terraform)

Unsupported Terraform file format

You will get this error if the imported repository contains HCL version 1 files. Snyk only supports HCL version 2, used from Terraform version 0.12+. Use the terraform validate command to check your configuration file version.

Articles in this section