info.message.replace is not a function when viewing a Component

Expected Behavior

I should be able to view my component in the catalog.

Current Behavior

After the last upgrade, I am getting a series of the same error, info.message.replace is not a function when viewing a component, this was working fine 2 releases ago.

Possible Solution

Steps to Reproduce

1. Open Component
2. Same error shows multiple times

Context

Your Environment

• NodeJS Version (v14): Node16
• Operating System and Version (e.g. Ubuntu 14.04): Win10
• Browser Information: Chrome and Edge

[regicsolutions]

@freben i have confirmed your fix in the latest release fixed my issue, Thank You!

[regicsolutions]

Thanks, ill give it another try with the latest release.

Question: This is how i have been using replaceProcessors in my backend catalog.ts (been working fine since release-2021-11-17.1)

  builder.replaceProcessors([
    new ScaffolderEntitiesProcessor(),
    new FileReaderProcessor(),
    BitbucketDiscoveryProcessor.fromConfig(env.config, {
      parser: customBitbucketRepositoryParser,
      logger: env.logger,
    }),
    LdapOrgReaderProcessor.fromConfig(env.config, {
      logger: env.logger,
      groupTransformer: customGroupTransformer,
      userTransformer: customUserTransformer,
    }),
    new UrlReaderProcessor({ reader: env.reader, logger: env.logger }),
    new LocationEntityProcessor({ integrations }),
    new AnnotateLocationEntityProcessor({ integrations }),
  ]);
  

Given FileReaderProcessor, UrlReaderProcessor and AnnotateLocationEntityProcessor are being returned as part of the getDefaultProcessors:

https://github.com/backstage/backstage/blob/c2da6492fb917002517a54638e1da6fa523f2a8f/plugins/catalog-backend/src/service/NextCatalogBuilder.ts#L289

Would i just add it like this?

  builder.replaceProcessors([
    new ScaffolderEntitiesProcessor(),
    BitbucketDiscoveryProcessor.fromConfig(env.config, {
      parser: customBitbucketRepositoryParser,
      logger: env.logger,
    }),
    LdapOrgReaderProcessor.fromConfig(env.config, {
      logger: env.logger,
      groupTransformer: customGroupTransformer,
      userTransformer: customUserTransformer,
    }),
    new LocationEntityProcessor({ integrations }),
  ]);
// Gets Default Processors 
    builder.getDefaultProcessors();