Same here: pretty annoying…
having it and not fixed. also having quota exceeded all the time with paid api keys
yes i am also getting same error
I also gone to google cloud and now its showing me publish site but then it shows something went wrong
Same thing here with that publishing error. What, if anything, is Google saying about this bug/issue? I have work to do, and I’m going to have to look at competitors (which I don’t want to do) to keep working.
Me too, cannot deploy new version for my apps
1 Like
O erro persiste!!! Não consigo publicar o meu app.
me encontro com o mesmo problema, ruim que ainda não há nenhuma nota oficial. Estou vendo como vou fazer um deploy manual.
Any updates? “Publishing is temporarily disabled while we work on system updates. Check back soon.” How soon is soon, do ya think?
2 Likes
still having deployment issue with AI sutdio
I am getting this too. Do we know any fix or workaround?
Its been days now without any explanation. Could someone from Google please let us know what is going on here? Should we all just pack up and move to other platforms at this point?
That‘s essentially what I‘m planning to, yeah
Guys please fix it 
i want to deploy my app, my clients are waiting 
Unable to publish for the last few days beginning on March 2nd. “Publishing is temporarily disabled while we work on system updates. Check back soon.”
Exceeding quota when testing “Failed to call the Gemini API: user has exceeded quota. Please try again later.”
Google Al Studio and the Gemini API Status is showing:
FULL OUTAGE for March 3-4
It’s not working for me either since a week.
YES!!! BEEN so Bad just wanna dump this service for others
“If your AI Studio publish fails, check Cloud Run logs. If you see PathError: Missing parameter name at index 2: /* (path-to-regexp), fix your server catch-all route: change app.get('/*', ...) to app.get(/.*/, ...), then redeploy and it fixed the issue”
I think the recent updates tanked somthing related to this post. I’ve been fighting with this for about a week. I was publishing fine, then out of the blue I got a notification about reaching model quota and after that it would not publish anymore.
At first I thought I needed to go back in versions…but I still couldn’t get anywhere. I started diving into the Cloud Run logs and using the Investigate log feature and eventually…after many prompts…I do have a Publishing app that was not Publishing for over a week.
I’ve kept a Remix of the Original app that would not publish and the Remix version that I have not trouble shot is still having the problem. This indicates to me that there was not a resolution on AI Studios side…Rather, it was a resolution to bad code in my app…even if it was originally intoduced by AI Studio.
The moral of the story is…I wouldn’t recommend a passive approch to a resolution. I don’t think there is something that can be patched easily…unless AI Studio can pinpoint the exact code without needing to have failed publish attempts that link you to Cloud Run logs.
BTW, here is the prompt that finally got me back publishing…if it’s any help:
MY PROMPT:
“My app has not been able to publish, here is an analysis of the problem. Can you fix it?:
PathError [TypeError]: Missing parameter name at index 10: /:splat(.*); visit https://git.new/pathToRegexpError for info
at name (/workspace/node_modules/path-to-regexp/dist/index.js:96:19)
at parse (/workspace/node_modules/path-to-regexp/dist/index.js:113:68)
at pathToRegexp (/workspace/node_modules/path-to-regexp/dist/index.js:267:58)
at Object.match (/workspace/node_modules/path-to-regexp/dist/index.js:237:30)
at matcher (/workspace/node_modules/router/lib/layer.js:86:23)
at new Layer (/workspace/node_modules/router/lib/layer.js:93:62)
at Function.route (/workspace/node_modules/router/index.js:428:17)
at Function.route (/workspace/node_modules/express/lib/application.js:257:22)
at app. [as get] (/workspace/node_modules/express/lib/application.js:478:22)
at startServer (file:///workspace/server.ts:181:9) {“
RESULTS:
“The issue persists because Express 5’s path-to-regexp syntax is very strict and has changed significantly. The previous attempts with string-based routes (*, (.*), /:splat(.*)) all failed due to parsing errors.
I have updated server.ts to use a Regular Expression (/.*/) for the catch-all route instead of a string. This bypasses the path-to-regexp string parser entirely and is the most robust way to match all routes in Express, regardless of version.
Action taken:
- Replaced app.get(“/:splat(.*)”, …) with app.get(/.*/, …) in server.ts.
Please redeploy your application. This should resolve the PathError and allow the container to start successfully.”
Didn’t work for me when I just tried it.
1 Like