Skip to content

Error messages if failed to upload customize files #1302

@macrat

Description

@macrat

Thank you for the useful tool!
I had a problem that was a bit confusing. So I want to share it.

Package

  • @kintone/customize-uploader 5.0.19

Why

Our environment have a proxy with authentication, but we don't have to use proxy when access to Kintone because it in the white list.
So, I had to remove HTTPS_PROXY environment variable before try kintone-custom-uploader out. And I forgot this.

I think this situation is exactly the same as when set wrong value to HTTPS_PROXY, or forget to set HTTPS_PROXY even if need it.

And then, I saw the below error message.

$ KINTONE_BASE_URL=https://xxxx.cybozu.com KINTONE_USERNAME=xxxx KINTONE_PASSWORD=xxxx ./node_modules/.bin/kintone-customize-uploader kintone-manifest.json --lang en
Start uploading customization files
Failed to upload JavaScript/CSS files
An error occured, retry
Start uploading customization files
Failed to upload JavaScript/CSS files
An error occured, retry
Start uploading customization files
Failed to upload JavaScript/CSS files
KintoneRestAPIError: [404] [GAIA_BL01] 指定したファイル(id: null)が見つかりません。 ([ID or something was here])
    at KintoneResponseHandler.handleErrorResponse (/path/to/project/node_modules/@kintone/rest-api-client/lib/KintoneResponseHandler.js:57:15)
    at /path/to/project/node_modules/@kintone/rest-api-client/lib/KintoneResponseHandler.js:35:123
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

I was very confuse by this error message because it said "Not found the specified file".
And took long time to notice that it is my mistake about the proxy.

What

I'm guessing the error message that I saw was caused from /k/v1/preview/app/customize.json API.
But the main problem in this case was the response of /k/v1/file.json was wrong.

I hope the command to show more meaningful error message if it failed to communicate with the Kintone server like this case, for the users can understand easily what happen.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions