#Upgrade from 1.43.1 to 1.44.2 Error on start

11 messages · Page 1 of 1 (latest)

young radish
#

Hi, is anyone encountering this error when you try to run yarn start?

2025-11-07T10:21:13.271Z backstage error Unhandled rejection Cannot read properties of undefined (reading 'id') type="unhandledRejection" stack="TypeError: Cannot read properties of undefined (reading 'id')\n at BackendInitializer.#doStart (C:\\DevWorks\\Backstage\\backstage\\node_modules\\@backstage\\backend-app-api\\src\\wiring\\BackendInitializer.ts:298:50)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async BackendInitializer.start (C:\\DevWorks\\Backstage\\backstage\\node_modules\\@backstage\\backend-app-api\\src\\wiring\\BackendInitializer.ts:245:5)\n at async BackstageBackend.start (C:\\DevWorks\\Backstage\\backstage\\node_modules\\@backstage\\backend-app-api\\src\\wiring\\BackstageBackend.ts:38:5)"

On my local, it will show this error message on console, then proceeds on loading the page, however once it is deployed to Docker, the container crashes and fails to startup due to this error, Resulting to 404 Not Found.

I've only encountered upon upgrade.,

image.png
young radish
#

Anyone who can help me with this?

soft moth
#

If you run yarn tsc do you see any errors?

unkempt smelt
#

Also did you run the upgrade helper? What dependencies changed between the versions? That would give you some real insight on why it may not be coming up

young radish
unkempt smelt
#

Is there still an issue?

serene dust
#

@unkempt smelt I have the same issue, although I'm upgrading from 1.43.3
It seems to be related to the plugin-scaffolder-backend package. If I remove the import in the backend, the error goes away. It also seems to have been bumped in v1.44.0.

#

I originally tried to upgrade to 1.45.0 when I got the issue, then tried different versions until the error started to appear

lament spoke
#

Hmm I wonder if this could be some form of circular import or duplicate versions. 🤔 such that when the initializer runs, the object given to it isn't constructed yet so it's undefined

serene dust
#

@lament spoke Do you have any idea on how I could investigate it? I have tried to run yarn dedupe and yarn.lock only contains one resolution entry for plugin-scaffolder-backend

lament spoke
#

Honestly it's tough from a distance. If you could make a stripped down minimal repo that we could clone and try out it would help