Service is now restored

Issues
1

We should be back up

2

Still looking into the root cause

3

@chungwu Hello! Having the same issue this morning for one project.

Has big business impact on our side.

Project ID and link are the following:
https://studio.plasmic.app/projects/fGkRH6KwFVx5gsJEbLnzjW

4

Issue seems to stem from catchall. Home page works fine, but catchall breaks for some instances

FetchError: invalid json response body at <https://codegen.plasmic.app/api/v1/loader/code/published?platform=nextjs&projectId=fGkRH6KwFVx5gsJEbLnzjW> reason: Unexpected end of JSON input
    at /var/www/node_modules/next/dist/compiled/node-fetch/index.js:1:51220
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async o.fetchLoaderData (/var/www/node_modules/@plasmicapp/loader-fetcher/dist/loader-fetcher.cjs.production.min.js:1:691)
    at async exports.PlasmicModulesFetcher.doFetch (/var/www/node_modules/@plasmicapp/loader-fetcher/dist/loader-fetcher.cjs.production.min.js:1:1887)
    at async exports.PlasmicModulesFetcher.fetchAllData (/var/www/node_modules/@plasmicapp/loader-fetcher/dist/loader-fetcher.cjs.production.min.js:1:1813) {
  type: 'invalid-json'
5

hmm is this still happening? I seem to be able to fetch without issues

6

Still happening for me indeed

image.png
image.png1076×362 29.2 KB

7

not sure if it helps, but console says

image.png
image.png1646×120 29.6 KB

8

@chungwu I’ve retriggert a release on our end and that seems to fix it. Maybe cache. Thanks for thinking along