No API factory available for dependency apiRef{core.scmauth} of dependent apiRef{plugin.catalog-import.service}
See original GitHub issueWhen trying to load the catalog import page, I am faced with “No API factory available for dependency apiRef{core.scmauth} of dependent apiRef{plugin.catalog-import.service}” error.
Expected Behavior
The catalog import page should load for me to import catalog entities.
Current Behavior

Steps to Reproduce
Output of yarn dev:
sang@TB-L161:~/Codes/backstage$ yarn dev
yarn run v1.22.17
$ concurrently "yarn start" "yarn start-backend"
$ yarn workspace app start
$ yarn workspace backend start
$ backstage-cli backend:dev
$ backstage-cli app:serve
[1] Build succeeded
[0] Loaded config from app-config.yaml, app-config.local.yaml
[0] <w> [webpack-dev-server] "hot: true" automatically applies HMR plugin, you don't have to add it manually to your webpack configuration.
[0] (node:88996) [DEP_WEBPACK_DEV_SERVER_CONSTRUCTOR] DeprecationWarning: Using 'compiler' as the first argument is deprecated. Please use 'options' as the first argument and 'compiler' as the second argument.
[0] (Use `node --trace-deprecation ...` to show where the warning was created)
[0] (node:88996) [DEP_WEBPACK_DEV_SERVER_LISTEN] DeprecationWarning: 'listen' is deprecated. Please use async 'start' or 'startCallback' methods.
[0] <i> [webpack-dev-server] Project is running at:
[0] <i> [webpack-dev-server] Loopback: http://localhost:3000/, http://127.0.0.1:3000/
[0] <i> [webpack-dev-server] Content not from webpack is served from '/home/sang/Codes/backstage/packages/app/public' directory
[0] <i> [webpack-dev-server] 404s will fallback to '/index.html'
[0] <i> [webpack-dev-middleware] wait until bundle finished: /
[1] 2021-11-03T15:49:38.629Z backstage info Loaded config from app-config.yaml, app-config.local.yaml
[1] 2021-11-03T15:49:38.642Z backstage info 0 secrets found in the config which will be redacted
[1] 2021-11-03T15:49:38.657Z backstage info Created UrlReader predicateMux{readers=azure{host=dev.azure.com,authed=false},bitbucket{host=bitbucket.org,authed=false},github{host=github.com,authed=false},gitlab{host=gitlab.tradebyte.org,authed=false},gitlab{host=gitlab.com,authed=false},awsS3{host=amazonaws.com,authed=false},fetch{}
[1] 2021-11-03T15:49:38.907Z auth info Configuring "database" as KeyStore provider type=plugin
[1] 2021-11-03T15:49:38.920Z techdocs warn The 'techdocs.generators.techdocs' configuration key is deprecated and will be removed in the future. Please use 'techdocs.generator' instead. See here https://backstage.io/docs/features/techdocs/configuration type=plugin
[1] 2021-11-03T15:49:38.921Z techdocs info Creating AWS S3 Bucket publisher for TechDocs type=plugin
[1] 2021-11-03T15:49:40.027Z catalog warn Processor BuiltinKindsEntityProcessor threw an error while validating the entity; caused by TypeError: /spec should have required property 'memberOf' - missingProperty: memberOf type=plugin entity=user:default/chris.slarke
[1] 2021-11-03T15:49:40.029Z catalog warn Processor BuiltinKindsEntityProcessor threw an error while validating the entity; caused by TypeError: /spec should have required property 'memberOf' - missingProperty: memberOf type=plugin entity=user:default/chris.williams
[1] 2021-11-03T15:49:46.424Z techdocs error Could not retrieve metadata about the AWS S3 bucket com-tradebyte-cps-backstage-techdocs. Make sure the bucket exists. Also make sure that authentication is setup either by explicitly defining credentials and region in techdocs.publisher.awsS3 in app config or by using environment variables. Refer to https://backstage.io/docs/features/techdocs/using-cloud-storage type=plugin
[1] 2021-11-03T15:49:46.425Z techdocs error from AWS client library Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1 type=plugin code=CredentialsError time=Wed Nov 03 2021 16:49:46 GMT+0100 (Central European Standard Time) retryable=true originalError=[object Object] stack=CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
[1] at Timeout.connectTimeout [as _onTimeout] (/home/sang/Codes/backstage/node_modules/aws-sdk/lib/http/node.js:69:15)
[1] at listOnTimeout (internal/timers.js:557:17)
[1] at processTimers (internal/timers.js:500:7)
[1] 2021-11-03T15:49:46.430Z proxy info [HPM] Proxy created: /test -> https://example.com type=plugin
[1] 2021-11-03T15:49:46.431Z proxy info [HPM] Proxy rewrite rule created: "^/api/proxy/test/?" ~> "/" type=plugin
[1] 2021-11-03T15:49:46.432Z search info Added DefaultCatalogCollator collator for type software-catalog type=plugin
[1] 2021-11-03T15:49:46.434Z app warn Can't serve static app content from /home/sang/Codes/backstage/packages/app/dist/static, directory doesn't exist type=plugin
[1] 2021-11-03T15:49:46.437Z backstage info Initializing http server
[1] 2021-11-03T15:49:46.441Z backstage info Listening on :7000
Please ignore the S3 credentials not found error, they are intentional when developing locally.
Your Environment
Output of yarn backstage-cli info:
sang@TB-L161:~/Codes/backstage$ yarn backstage-cli info
yarn run v1.22.17
$ /home/sang/Codes/backstage/node_modules/.bin/backstage-cli info
OS: Linux 5.11.0-38-generic - linux/x64
node: v14.18.1
yarn: 1.22.17
cli: 0.8.1 (installed)
Dependencies:
@backstage/backend-common 0.9.8
@backstage/catalog-client 0.5.0
@backstage/catalog-model 0.9.6
@backstage/cli-common 0.1.5
@backstage/cli 0.8.1
@backstage/config-loader 0.7.1
@backstage/config 0.1.11
@backstage/core-app-api 0.1.19
@backstage/core-components 0.7.2
@backstage/core-plugin-api 0.1.12
@backstage/errors 0.1.4
@backstage/integration-react 0.1.13
@backstage/integration 0.6.9
@backstage/plugin-api-docs 0.6.12
@backstage/plugin-app-backend 0.3.18
@backstage/plugin-auth-backend 0.4.6
@backstage/plugin-catalog-backend 0.17.2
@backstage/plugin-catalog-import 0.7.3
@backstage/plugin-catalog-react 0.6.2
@backstage/plugin-catalog 0.7.2
@backstage/plugin-github-actions 0.4.22
@backstage/plugin-org 0.3.27
@backstage/plugin-proxy-backend 0.2.13
@backstage/plugin-scaffolder-backend-module-cookiecutter 0.1.3
@backstage/plugin-scaffolder-backend 0.15.11
@backstage/plugin-scaffolder-common 0.1.1
@backstage/plugin-scaffolder 0.11.9
@backstage/plugin-search-backend-node 0.4.3
@backstage/plugin-search-backend 0.2.6
@backstage/plugin-search 0.4.16
@backstage/plugin-tech-radar 0.4.11
@backstage/plugin-techdocs-backend 0.10.7
@backstage/plugin-techdocs 0.12.4
@backstage/plugin-user-settings 0.3.10
@backstage/search-common 0.2.1
@backstage/techdocs-common 0.10.5
@backstage/test-utils 0.1.20
@backstage/theme 0.2.12
@backstage/types 0.1.1
@backstage/version-bridge 0.1.0
Done in 0.38s.
- NodeJS Version (v14): 14.18.1
- Operating System and Version (e.g. Ubuntu 14.04): Ubuntu 20.04
- Browser Information: Agnostic
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
catalogImportApiRef · Backstage Software Catalog and ...
Utility API reference for the CatalogImportApi. Signature: catalogImportApiRef: import("@backstage/core-plugin-api").ApiRef<CatalogImportApi> ...
Read more >@backstage/plugin-catalog-backend - npm
The Backstage backend plugin that provides the Backstage catalog. Latest version: 1.5.1, last published: a month ago.
Read more >Tutorial: How to use your company's component library with ...
Even if you're not using the UI components of Backstage plugins, ... API available in your application by adding an API factory to...
Read more >backstage/backstage release-2021-03-18 on GitHub
plugins /catalog-backend/src/service/router.ts:117:17) ... will be seen in the frontend, on the form No API factory available for dependency ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I saw this when bumping versions and not applying the change in the changelog referenced above. Applying the change fixed it.
Can you check if you this change was applied to your instance after updating the backstage packages? https://github.com/backstage/backstage/blob/master/plugins/catalog-import/CHANGELOG.md#070