In Architect 2.0, when defining an override, a requires statement was added to app.js so the override is loaded first.
In Architect 2.1, that statement was removed in favor of a requires statement inside the overridden class itself, which causes Ext.Loader to attempt to load the override asynchronously.
This is fine in a development environment but causes problems in production. The Sencha build tools prioritize the order of a build by the order in which they are loaded by Ext.Loader. This means I see the following in my jsb3:
This causes AllEvents to be loaded first, which then attempts to asynchronously load the override because it hasn't been registered yet.
In my production build this is causing errors in the JS console. It doesn't appear to be adversely affecting functionality, but the borked AJAX call and the resulting error can be avoided.
Edit: Great job on 2.1! That was one of the smoothest upgrades I've ever had for Architect, and one of the most feature-packed as well.