Cannot re-enter 'dev' mode through retool-ccl

💬 App Building
,
1

I have seen similar posts regarding how to properly handle this problem, but haven't come across any solutions for the recommended troubleshooting steps.

Issue:
After recent deployment of existing components within our custom component library via running npx retool-ccl deploy at the retool-custom-component-library/new-custom-component/ level, I can no longer see any changes I make to components in the existing library once running npx retool-ccl dev. The only way I am ever able to see current changes now is if I, again, run npx retool-ccl deploy after making changes -- which is not ideal.

  • :memo: Note: In the settings of each of our retool apps that uses a custom component, I do have each environment set to dev:example.email@companyname.com

Solutions I have tried:

  • Using control + C to force exit dev mode and re-rerunning npx retool-ccl dev.
  • Completely logging out and back into everything by executing the following steps:
    1. Logging out of retool via retool logout;
    2. re-authenticating successfully w/ retool login using cookies credentials via xsrfToken and accessToken values;
    3. running retool whoami to confirm authentication values;
    4. successfully re-logging in via npx retool-ccl login;
    5. reinitiating dev mode.

I would very much appreciate some guidance here so I can keep seeing live changes in dev mode, and avoid having to deploy every time I want to see changes I've made to a custom component in our library.

Thank you in advance!
AJ Vancattenburch

1 Like
5

Hi @AJVancattenburch FYI, I just found a quicker (not ideal) solution by:

  • Opening devtools
  • With devtools opened right click on refresh page icon button and select “Empty Cache and Hard Reload”

That worked for me, hope it helps

1 Like
6

Hi @AJVancattenburch,

I don't see a known bug here. Did @Javier_Ceballos's suggestion resolve things for you? :crossed_fingers:

1 Like
7

I found out the reason why was because our org currently uses a version of retool that has issues spinning up the dev env for custom components, and we haven't updated to the version where the fix lives yet.

There's been a lot of other projects that have taken precedence over analyzing changelog differences to ensure they align with the rest of our current org configurations so we can continue custom component development. As soon as we are able to move to the version where the supposed solution lives, I'll update this post with results!

Since we've been so busy completing other tasks, I haven't even had time to touch our library since I created this post last month. So I'm honestly not sure what the current behavior is or if it has changed.

1 Like
8

Fair enough; thanks for the update!

1 Like