Use both analysis engines

Has your canvas app ever crashed in the player? Check both analysis engines! Today was a day of rubberducking and headscratching. Solution on dev was fully working, released to test and prod via pipeline, caused a crash on load - app monitor says almost nothing, console log says function rendering containers crashed. You have no idea what to do... The issue? It turned out that one of the developers created a named formula with the same name as a collection. The best part? The app was on a new analysis engine and returned no errors in the studio. Switching back to the old analysis engine gloriously returned an error and saved my days after a few hours of frantically searching everything. Conclusion? When you don't know what else to do to fix your code that you are confident should work, check both engines. Having two engines in the studio allows for finding even more errors than we were able to find only via the old one. While Microsoft is still making efforts to make the new one as good as possible, and even if it's been in GA for a few months, there may always be some bugs or untraced errors. In this case, I was able to find full reproduction steps, which are now submitted to the Microsoft Engineering Team. As always, deployment of such a change in the natural process may take 2-3 months to get it fully to production studio instances. As long as both engines are accessible, make it your good development practice to check them once in a while to keep hygiene in your code!