Can't update version of custom component library

💬 App Building
1

  1. My goal:
    Update the version of my custom component library

  2. Issue:
    I am setting it to the newest version, Network tab also confirms that it was successful. While building the App it also has the correct version, but on a page reload it jumps back to the old one.
    It randomly does save it to the correct version, but only after hours of setting it and hoping for the best.
    It does work normally on fresh projects.

  3. Steps I've taken to troubleshoot:

  • Logged out all users
  • Stopped all dev syncs from the cli
  1. Additional info: (Cloud or Self-hosted, Screenshots)
  • Cloud
3

Hi @Ed_Korenblum,

That is very unusual that the networking request confirms that changing the custom component version in the UI was successful, but that later on page reload the version changes back to the older version :thinking:

I don't think I have seen this before. Some code must be trying to override the newest version with a previous save of the app with an older version. Are you using version control and if so, how are you using it?

In 'Releases' have you created a new release with the newest version selected? One guess would be that the release had saved the older version and it may be checking the release on page refresh.

Thank you for testing this on other projects, if other projects work fine then I think the app may be in a corrupted state. Hopefully creating a new release can get the app out of this corrupted state but as a worst case scenario you may need to export/import your components and logic of the app to another app.

1 Like
4

Hi @Jack_T,
I have the same issue in my project.
I am not using version control, but simply the Retool editor.
I have created a new release and verified in “Compare changes”, that the "collectionRevisionUuid" has changed. Howevery, when I reloaded, there was the old version in the custom component. When I set this to the current version afterwards, the “collectionRevisionUuid” does not change.
The problem was resolved automatically a few hours later. Then, the newest version was active.

5

Hi @MartinSperr,

Thank you for letting me know! I can investigate this further. Let me know if there are any additional steps I should follow to reproduce other than creating two versions of a custom component, changing from the old version to a new version and then reloading the page and inspecting the uuids.

That is very curious that the problem was resolved automatically a few hours later. That makes me think there may be some kind of state cache which the app is falling back to for versions when page reloads occur.

Obviously the page should properly update and save the current version of the custom component so there is some type of bug, just need to reproduce it.

6

Hi @Ed_Korenblum and @MartinSperr,

I did some digging and this seems to be a known bug that our engineering team is working on addressing.

The engineering team is keen to take a look at a HAR file if you can share one from your app when this behavior occurs.

Also the engineer had mentioned "One thing that would be helpful to confirm is if the user can see the library version update consistently if they wait, say, 30 seconds after changing the dropdown value before refreshing the page.

We had suspected that there might be some amount of latency preventing the save from going through such that the update wasn't persisted."

10

Hello folks @Ed_Korenblum, @MartinSperr,

I got word from the engineering team that this ticket is complete!

It should be solved where once you specify the version it should stay consistent. Let me know if you are still experiencing this issue and I can ping the engineers!