11 Dec 2012 3:39 AM #1
Could not find master instance -> work lost!
Sencha Architect 2.1 r676 on os x.
My project has multiple linked instances to a component (just an extended Ext.dataview.list where I override the prepareData method). If I (save and then) close sencha architect and re-open the project, at least 1 of my linked instances will not be found and it'll automatically remove the component from the view (along with the new code in prepareData).
The error displayed is:
Could not find master instance ExtBox1-ext-gen2866 for linked instance "component" - the linked instance will be removed.
Happens every damn time, particularly frustrating because I have to quit Sencha Architect on occasion to get it to stop closing the current file I'm working on after I've edited a resource (this is another bug though, which someone else has already posted.)
Edit: am going to prepare another test project that I'll upload here that'll allow you to reproduce this. Right now this is basically stopping me from getting any work done, as on reloading some random part of my project is simply removed and code is lost.
edit 2: attempting to reproduce this on a new project isn't giving me the error. Something must be screwed with my real project file, in which added components are not found. Any way I can help you guys debug this? Thanks.
11 Dec 2012 11:12 AM #2
13 Dec 2012 7:01 AM #3
Sent you an email with the project. 2 zips, one causes a call stack overflow, the other has the behaviour described.
23 Jan 2013 4:24 PM #4
Hi coolfish, we're still investigating possible causes of your issues but I wanted to give you an update on our findings so far.
In the project that has the stack overflow, this is because somehow you have a linked instance that is a child of its own master instance (in MyNavigationView12). I'm trying to find how it could have gotten into this situation, because this should never be allowed -- if you have any idea what steps you took to get it in that state please let us know. However, you should be able to get the project back into a useable state by doing the following:
- In a text editor, open the file metadata/view/MyNavigationView12
- Delete the object within the "cn" array that has type:linkedinstance so it's just an empty array ("cn": )
- Save the metadata file and open the project in Architect, it should now open correctly
- Re-link whatever component was supposed to be the child of the navigation view, if any.
Sencha Architect Development Team
25 Jan 2013 6:32 AM #5
I'm not sure how I got it to get an instance to link to its child instance. That state happened while preparing the project which resulted in a loss of data when a new custom component was added to the project. To avoid the data loss, I make sure that the userAlias and userClassName is unique for the newly added custom component before saving & reopening the project. Try adding more than one instance of the custom component into the project.
Hope this helps
25 Jan 2013 10:03 AM #6
It sounds like you've got some custom components saved to the toolbox which you're using to create new instances -- it's possible that the problem lies there. Would you be able to send us a copy of those custom toolbox components so we can inspect them for issues? (Right-click custom toolbox item -> Export to file)Jason Johnston
Sencha Architect Development Team
13 Dec 2012 11:19 AM #7
Thanks for the projects, this will help us look into the bug.