App.js Contains Non-Existent View

[brian.scott@talgov.com]

Hello friends -

Please see the attached screenshot. App.js is referencing a class that I added to the project at one point, but have since deleted. Unfortunately, I cannot pare the value out of app.js from within Architect. Of course, I could do it manually outside of the tool, but then every re-publish I have to manually touch the file.

Is there a way to clean the app.js file to actually understand if something has been removed from the project?

Am I missing something / has anyone else run into this?

brian

[brian.scott@talgov.com]

Note to anyone who comes into this. It can be 'solved' by killing Architect, the goto your workspace, then metadata folder, then open Application in a text editor. Remove the invisible entry, refire up Architect and the value is gone. Note: You must edit the file in /metadata, just going after /workspace/app.js will not work.

brian

[aconran]

Brian -

This should definitely not happen. Thanks for sharing your workaround.

If you are able to reproduce steps that make this occur reliably, please let us know. In the mean time, we will be on the lookout for this issue.

[tyladurdan]

This happens a lot, I'd have thought this would have been picked up by now by the bug tracker...

The problem happens with me after having about 5 or 6 views with the same amount of stores. When deleting one of them, hitting save...sometimes even when archiving a project. When opening the archived the program still has references to previous deleted stores, models views etc in the app.js part. The problem can be fixed by looking at the config in the root of the app.js part, in the config section there are still references to deleted stores/views/models etc (they all have blank icons). They can be removed with the 'x' delete button and and a resave fixes it.

The solution for me has been to archive the project after each key major update, just in case you can restore easily.

This can be random, but can happen occasionally whilst experimenting and adding new views/stores/models to a project but then deleting.

To reproduce the problem try adding a new part to your app e.g. A twitter feed with model, store view. Save. Archive the project. Save. Remove the twitter view, model, store. Save, archive project. Try and reimport the archive and test and see if it still has a reference to the deleted items.

:-)

[andrew.cognisolve]

I've had a similar issue where after renaming various views and saving, the app.js maintains references to the old names. Modifying the Application file as suggested in the workaround to match the new names fixes the problem for me. I've not noticed any particular pattern to when app.js updates appropriately and when it does not. I just save, run the app in chrome and get a failed GET since it points to a non-existent js file.

[aconran]

We believe we've fixed this with 2.2. If you see this come back with the release (coming soon) please let us know.