Custom Component upload failing

App Building
1

  • Goal: attempting to upload custom component to retool via retool cli.

  • Steps: retool build works fine (Build Succeeded) -- have tried clearing global npx cache, deleting node_modules, wiping dist.

When re-running Init against the name of a deleted Custom Component Library, the namespace appears to still be in use on Retool's side.

  • Details: "Sending updated code to Retool"... hang indefinitely for both deploy and dev commands.

  • Screenshots:
    Screenshot 2024-10-01 at 2.53.15 PM

  • App json export: (here's how to get a json export)

5 Likes
2

Additional detail: when the request times out this is the error:
Error creating new version of custom component library:
Error happened while building: Build failed with 1 error:
/Users/****/Desktop/retool/node_modules/@tryretool/custom-component-support/apiError.js:46:19: ERROR: [plugin: zip-and-send] Error

3

I'm having this issue as well, same scenario where I changed the component name to be something more meaningful and it hangs on the upload:

image
image774×322 27.2 KB

4

  • Goal: want to update existing custom component in app

  • Steps: 1. have an existing custom component, 2. upgrade the @tryretool/custom-component-support npm package to latest 1.1.0 version, 3. run npx retool-ccl dev in bash, 4. after long waiting [ERROR] Error [plugin zip-and-send] /node_modules/@tryretool/custom-component-support/apiError.js:45:19:
    45 │ return new ApiError(Failed to connect to the url. The error was: ${JSON.stringify(e, null, 2)}.);

  • Details:

  • Screenshots: /Users/gabor.soos/workspace/retool-custom-component/node_modules/@tryretool/custom-component-support/apiError.js:45:19:
    45 │ return new ApiError(Failed to connect to the url. The error was: ${JSON.stringify(e, null, 2)}.);
    ╵ ^

    at handleApiError (/Users/gabor.soos/workspace/retool-custom-component/node_modules/@tryretool/custom-component-support/apiError.js:45:20)
    at CustomComponentLibraryWrappedClient.request (/Users/gabor.soos/workspace/retool-custom-component/node_modules/@tryretool/custom-component-support/customComponentLibraryWrappedClient.js:47:56)
    at async CustomComponentLibraryWrappedClient.customComponentLibrariesLibraryIdRevisionsPostRaw (/Users/gabor.soos/workspace/retool-custom-component/node_modules/@tryretool/custom-component-support/retool_client/apis/CustomComponentLibraryApi.js:216:26)
    at async CustomComponentLibraryWrappedClient.customComponentLibrariesLibraryIdRevisionsPost (/Users/gabor.soos/workspace/retool-custom-component/node_modules/@tryretool/custom-component-support/retool_client/apis/CustomComponentLibraryApi.js:229:26)
    at async /Users/gabor.soos/workspace/retool-custom-component/node_modules/@tryretool/custom-component-support/build_components.js:223:40
    at async /Users/gabor.soos/workspace/retool-custom-component/node_modules/esbuild/lib/main.js:1495:27

    This error came from the "onEnd" callback registered here:

    /Users/gabor.soos/workspace/retool-custom-component/node_modules/@tryretool/custom-component-support/build_components.js:218:18:
    218 │ build.onEnd(async (result)=>{
    ╵ ~~~~~

    at setup (/Users/gabor.soos/workspace/retool-custom-component/node_modules/@tryretool/custom-component-support/build_components.js:218:19)
    at handlePlugins (/Users/gabor.soos/workspace/retool-custom-component/node_modules/esbuild/lib/main.js:1293:21)
    at buildOrContextImpl (/Users/gabor.soos/workspace/retool-custom-component/node_modules/esbuild/lib/main.js:979:5)
    at Object.buildOrContext (/Users/gabor.soos/workspace/retool-custom-component/node_modules/esbuild/lib/main.js:787:5)
    at /Users/gabor.soos/workspace/retool-custom-component/node_modules/esbuild/lib/main.js:2197:68
    at new Promise ()
    at Object.context (/Users/gabor.soos/workspace/retool-custom-component/node_modules/esbuild/lib/main.js:2197:27)
    at Object.context (/Users/gabor.soos/workspace/retool-custom-component/node_modules/esbuild/lib/main.js:2037:58)
    at buildAndDeployDevContiniously (/Users/gabor.soos/workspace/retool-custom-component/node_modules/@tryretool/custom-component-support/build_components.js:337:48)

5

I am having the same issue after upgrading @tryretool/custom-component-support package to latest this morning, it was working fine but it does not sync anymore.

6

I've uploaded the detailed error here Unable to upload Custom Component

7

We're having the same issue after updating the @tryretool/custom-component-support to v 1.1.0 . The operation is stuck on Sending updated code to Retool :incoming_envelope:... Downgrading the tool doesn't help, since previous version is rejected by ReTool service

8

Me too, rolling back seems to be unhelpful as well

9

We're seeing this as well. Currently blocking our dev :frowning_face:

2 Likes
10

We've also been seeing this since yesterday afternoon.

11

Same issue here. Custom Component upload worked on Sept 30.
As of Oct 1, using the same API key, I can no longer upload custom components. the CLI tool hangs on "Sending updated code to Retool"

12

Hey all! Thanks for flagging this so quickly. We are investigating internally and will provide an update here as soon as possible. :+1:

1 Like
13

The fix is coming, we will update here once it's live. Really sorry about the disruption!

2 Likes
14

We've fully recovered now, with the new version that's just deployed on cloud. Feel free to ping us still!