Thank you for reporting this bug. We will make it our priority to review this report.
Hey elgs -
We are still investigating this and have been unable to reproduce.
Do you have any additional information for us from the ticket you filed the other day?
If you can reliably make it happen, perhaps we can do a remote web session this week so that we can see it happen and figure it out.
Sencha Premium Member
I think I got some more information about this problem. It seems like it's the svn commit caused the references to be lost in the SA. I observed the following situation happened:
1, Open my SA project, work with it for a while, without any problem;
2, Save and publish the SA project. The publish target folder is managed by Eclipse/Subclipse(an eclipse based svn client);
3, Commit all changes to the SA project to the svn repository, including the project files and published files in Eclipse;
4, Now when I come back to SA, the reference to the controller is lost;
I guess at this moment, if I accidentally saved the SA project, I may permanently lose the files.
And I guess svn client should only do write access to its own .svn folder. If this is the case, what I'm wondering is whether SA monitors all files under its project folder, or only the relevant files?
SA monitors all of the metadata files and the overrides. I'm going to try to reproduce this issue.
Apologies elgs but are you windows or os x I forget?
I'm actively trying to reproduce the issue now. Are you able to see entries in the log stating files were removed?