View Full Version : [FIXED] Error on Save
24 Mar 2012, 8:12 AM
Using .337: Selecting save always results in this error:
This error began after the Designer trial period ended and this error occurred on the previous version of the Designer. I was told that this issue was resolved in the 337 release but it seems not - or is this an inconsistency in my project that is causing the problem?
24 Mar 2012, 12:13 PM
Hi, Is it possible to send to send a screenshot starting from splash window? Normally you should be seeing the splash window stating the trial has expired and giving you options to purchase the product.
24 Mar 2012, 12:30 PM
24 Mar 2012, 12:38 PM
Thanks for the report. I am moving this to bugs.
24 Mar 2012, 1:05 PM
Hi,Need more details here as i am not able to reproduce.My assumption based on your screenshot is your Trial is expiring today?Is that a new Project or existing you are saving? Can you try to create a new project and save? I want to see if this is something specific to the project you have. We may need a copy of that to resolve this issue.Thanks
24 Mar 2012, 2:26 PM
The trial ended several days ago. Well before the release of 337.
Also, the error does not present on a new project.
More information: copied the project to another computer (from win7 to Mac) and tried to save with an expired Designer trial. Save failed. Other test project exist on the Mac and they have no problem saving. Almost certainly a problem with the project contents.
24 Mar 2012, 3:21 PM
Could you send us the project that triggers the problem?
24 Mar 2012, 4:21 PM
the .xds file?
25 Mar 2012, 11:49 AM
You should not be able to open the project if your Trial is expired.
Do a File/Archive Project and send the xda file to designer dot feedback at sencha dot com
25 Mar 2012, 12:31 PM
send the file where?
25 Mar 2012, 5:33 PM
25 Mar 2012, 8:03 PM
26 Mar 2012, 4:47 AM
I noticed last night that loading the project and selecting Application in the Project Inspector followed immediately by clicking the Code view button causes this same error.
26 Mar 2012, 7:57 AM
I am able to reproduce this bug in build 337, but not in our current development branch. This bug will be fixed in the next release.
26 Mar 2012, 8:02 AM
Is there a chance of a work-around. No progress is possible until this issue is resolved.
26 Mar 2012, 8:18 AM
The workaround is to remove the Ext.define from the launch method of the designer.js file from an external editor.
Powered by vBulletin® Version 4.2.3 Copyright © 2016 vBulletin Solutions, Inc. All rights reserved.