Dynamic catch-all routes not supported in Google App Engine

[sanders54]

Issue with filename-name causing deploy error in Google App Engine

Describe the bug

I've had a nextJS app running in the Google App Engine enviroment for a while. Works splendid and fast - however, I added a dynamic route and now I am unable to deploy due to the filename being unsupported (due to the 3 dots).

Error from the Gcloud CLI:

ERROR: (gcloud.app.deploy) INVALID_ARGUMENT: Filename cannot contain '.', '..', '\r', start with '-', '_ah/', or '\n': pages/[...slug]/index.js.

One fix could be using underscore or similar instead, like "[___slug]"

To Reproduce

Deploy the app to Google App Engine using any boilerplate configuration for app.yaml with a dynamic catch all route. Use below example and add a catch-all page.

https://github.com/superbmeteor/nextjs-gae-demo

Expected behavior

Should deploy successfully.

[wieringen]

I'm also having this problem. The problem only occurs on the App Engine Standard environment.

[gmosx]

Now, this is extremely annoying :(

[B1rch]

I'm running into this problem right now as well. Any known workarounds would be greatly appreciated

[jeroenoomsNL]

Same problem here! It's blocking our project at the moment.

[sanders54]

Same problem here! It's blocking our project at the moment.

Same here. One workaround is to duplicate code for every sub-path (I did for 3 levels)

[jeroenoomsNL]

Same problem here! It's blocking our project at the moment.

Same here. One workaround is to duplicate code for every sub-path (I did for 3 levels)

Do you have an example of what you did to achieve this?

[wieringen]

I think he created the same workaround I did. Import and directly export the associated route component in every subpath, which in essence will duplicate that component for every subpath.

[sanders54]

That's correct - I didn't see this before now.

[dorli]

Anyone has a workaround without duplicating code for every path ?

[sanders54]

Anyone has a workaround without duplicating code for every path ?

Not that I'm aware of. Hopefully this is fixed soon!

[xe4me]

This is blocking our production release :(

[mykolat]

+1

[jsiddiqui]

I made the following workaround and it seems to work fine.

"gcp-predeploy": "find .next -name '\\[...*' -exec bash -c 'mv \"$1\" \"${1/.../@@@}\"' -- {} \\;",
"gcp-build": "find .next -name '\\[@@@*' -exec bash -c 'mv \"$1\" \"${1/@@@/...}\"' -- {} \\;",
"start": "next start -p ${PORT:-3000}",

Invoke yarn gcp-predeploy after building and before deploying to change ... to @@@ for uploading. The gcp-build steps renames it back on the app-engine instance. A small disadvantage of having a gcp-build step is that all dependencies are installed (including dev) for the gcp-build step and then cleared and then again for the start step, slightly increasing instance startup time. Note that we cannot rename inside the start script as the file system is read-only at that time.

[sanders54]

... slightly increasing instance startup time. Note that we cannot rename inside the start script as the file system is read-only at that time.

How much increased startup time did you see? I have an application where every MS counts.