Your deployment failed due to an internal error on our side when processing the registry credentials for Google Artifact Registry. This failure is also what's causing the dashboard to be stuck in a loading state for that project. We've flagged this to our engineering team for a fix. As a workaround, you may be able to create a project with a placeholder image first (e.g., from us-west1-docker.pkg.dev), then update the image URL and credentials in the service settings afterward.

I did what you told me by creating a new project with us-west1-docker.pkg.dev and change it to asia-southeast1-docker.pkg.dev, it's also stuck in the deployment. Now I have two projects with infinite loading state 😅

At this point, I'm not able to use Railway at all

...QQ, how long is your artifact registry password?

Artifact registry password is a JSON value. So it's make sense to have a long value

Hey, we pushed a fix for this, and your project should no longer be stuck in a loading state.

Alright. My project is not stuck anymore in a loading state and I am able to deploy a new service with the Docker image from the registry

But still one remaining issue left, which is I am still not able input asia-southeast1-docker.pkg.dev as the image URL when initiating project. I need to insert us-west1-docker.pkg.dev first, and then change it manually which is not a good experience. Are you guys have a plan to fix that?

We will have a fix out for that shortly.

Please let me know on this thread whenever it's fixed. Thanks

Should be live in about 10 minutes.

Cool it works now. Thanks for the help, Railway team!