Migration to multipage app has broken all previous releases of the app

💬 App Building
1
  1. My goal: To continue using my app releases
  2. Issue: I upgraded the app to multipage app. The app continued to work fine few at least a few weeks. Now, suddenly I am noticing the app will not boot up into any of the releases and gives and error about not being able to load the page. It seems like the app it always trying to load a page from the multipage version of it even though I am loading releases that were made before the app was migrated to multipage.
  3. Steps I've taken to troubleshoot: Tried loading releases. I have also tried restoring the app from a release and the system gives an error about not being able to restore.
  4. Additional info: I am on the cloud version

The message I am getting when trying to restore is.

Could not restore save

Cannot read properties of undefined (reading 'appTemplate')

2

Hi @Shawn_Crocker, this looks similar to some other threads I've seen recently on page saves and potentially old modules. @Erin_Masatsugu thoughts?

3

I finished rewiring some things in the app and I have created a release. The new release is working but the old ones still not. What I did notice a few weeks ago when I initiated the migration to a multipage app is, the app wouldn't change. I accepted to upgrade the app but them the app was always remaining as a single page. I then would try again to get it to upgrade. In my change history there a three occurrences one after the other showing the migration to multipage label. The other weird thing is, we have used this app in its older release state many times since I had upgraded the app workspace. It was only in the last week or so that it seemed to suddenly be unhappy about something.

4

Hm yes the "Could not restore save" error when trying to restore to a previous version usually means that the version you're trying to restore to is referencing a deleted module.

I'm glad the new release is working for you -- if you still want to be able to revert to the previous ones, if you share the page UUID we can try to restore your deleted module.

5

Ah yes. That makes sense. I had forgotten I had started cleansing the app of a problematic module. I had deleted the module prematurely. I was going into edit mode on the module and looking at apps that were using it. Then I was editing each app to strip it out. I had removed the module from this particular app but then left the app for awhile to do other things and forgot about it. I think it's worth noting that a module will report it isn't being used in an app even when the most recent, published release of an app is using it. It seems like if an app has a published release that references the module, that should be the criteria a module uses to report it's use within the app. In my other focus at work, I use the CAD system Onshape. I think I'm a little spoiled with how it treats versioning and releases. In Onshape, if something is referencing a version or release of something else, it will forever be able to reference that thing even if that thing is physically deleted from the system. It would be cool if retool releases worked similarly. It seems like an app release should capture all the code needed to function and not rely on the outer referenced items existence to continue functioning.

6

Thanks for explaining, and agreed this is all great feedback! Will log with the team to:

  • look into a module not being reported as used even if a published release of the app is referencing it
  • allow deleted modules to work within an existing app
1 Like