Could not load app - Invalid yaml


All of my apps that depend on this application cannot run. Changed nothing in this app for over 2 months.

All of a sudden all my apps are down because this app cannot load. All of the other apps show the following:
image

Nothing changed on my end, please assist.

Trying to remove the dependency then gives this error:
image

Seeing this error on one of the apps. App was working fine before.

Most of the older versions are broken too. So for, only branches more than a few months old are able to be loaded.

Hello,

I have the exactly same problem.

Hope this will be resolved soon.

All the best

Hi @divyeshlakhotia,

Could you supply an app ID and a couple of git SHAs to support@anvil.works please? Looks like something has gone very wrong here…

OK, we’ve managed to pull out a reproduction case from the logs, and we’re rolling back the relevant change. Sorry about this, folks!

Current hypothesis is that this affects users who made a manual edit to a YAML file in their app - possibly a long time ago - and a version change to Anvil’s YAML parsing caused that to go from “parses fine” to “raises an error as invalid”. Sigh.

Can people please now check whether this has resolved the issue?

1 Like

@meredydd Thank you very much for your immediate response.

I would just like to mention that I did not make any changes to the app, including any manual changes to its YAML files. The app was working normally and then suddenly became inaccessible.

My app(s) still not working.

Same, still not working.

Repro cases please! The error we initially identified appears to have stopped, so if it’s still going right now something else is afoot, so we really need precise reproduction instructions.

Up and running now, I updated the dependency app that was causing the issue to the new layouts and then could get it to load again.

Update: We’ve identified a place where our caches might have been retaining the error even though it’s now fixed at source. This would affects dependencies with the edited YAML, which is the pattern @Neeco was seeing. We’re flushing those caches now, stand by.

Again, I am begging for app IDs and repro instructions here if anyone is still broken. This is something that was (clearly!) outside our test cases. We spotted one thing based on these reports, resolved it, and now we’re kinda flying blind, because everything we’ve tested has been working the whole time!

3 Likes

OK, in the absence of repro instructions we’ve had to break out the Big Hammer and restart the entire cluster to clear all the caches. Apologies for the brief interruption to all apps, and slow launches of server code as the Thundering Herd comes through.

Everything should now be back to normal. Please let us know if it’s not.

1 Like

Solved! Thanks a lot! (The blind update seems to have worked)

Thanks for the quick fixes!

If this is an update which needs to be eventually made, a detailed traceback pointing the exact form or place with the corrupted yaml will help with debugging where things went wrong.

Maybe making this a manual migration for old apps (Like the layout migrations) so that we can test and fix things beforehand.

Would be happy to provide App IDs if needed for future investigation

Sorry, my apps are still not working. I sent app IDs.
Although, now Version History is available and I can load previous versions…

@stevan.armakovic THANK YOU. (You are the first person in this thread to provide an app ID!) We will investigate and reply by email.

1 Like