Well, 4 years later and we are still here. I’ve got a layer that has to be exported and manually combed through as the Preview + Commit + Publish workflow has completely broken down after adding 3 panel card grids. Changes save, can be exported, but no new changes show in preview - it gets stuck showing the same thing. Nothing to do with cache, there is an exception thrown when publishing the change, but since this is cloud, the inner exception isn’t available. I doubt that’s going to provide the actual answer, however.
I can tell in the export already that the grid has multiple entries. Deleting the 3 grids added doesn’t have any effect, so I assume the corrupted, malformed, or untracked JSON isn’t going anywhere unless manually corrected.
I face issues constantly in 2024.2, I had hoped this was resolved in K2025. Here’s hoping all work isn’t lost!
I frequently run into the issue where you cannot preview or publish, but typically save + close completely out of application studio + reopen is enough to get it fixed.
Makes ya wonder though, are they really eating their own dog food?
Yeah, that one is fun and frequent in 2024 - not sure I’ve experienced it in 2025.1 yet. This issue actually previews and saves changes, just not commit or publish. The client throws no indication, on browser you can see the console throws a 400. I am able to find the log in server, but it doesn’t contain the inner exception so it’s going to have to route through support.
I no longer get index errors spamming my console, so I think the layer self-corrected in a manner, but whatever was left behind is causing this “ghost” error. It would be nice if it alerted the user of such errors, though I figure this must not be an anticipated error path in App Studio.
