How to Report an Issue With Sencha Cmd

[dongryphon]

Reporting bugs for Sencha frameworks is well covered in this thread: http://www.sencha.com/forum/showthre...o-report-a-bug

Reporting bugs for Sencha Cmd is a bit different since it is a command line tool and not a browser UI framework.

Common Issues

Get the latest version of Sencha Cmd here: http://www.sencha.com/products/sencha-cmd

Read the guides before diving in - Cmd w/Ext JS and Cmd/Sencha Touch 2.1.

Sencha Cmd works with these versions of Sencha frameworks:

• Ext JS 4.1.1a
• Ext JS 4.1.2a
• Ext JS 4.1.3
• Sencha Touch 2.1.0
• Sencha Touch 2.1.1

If you are using Sencha Touch 2.0, you need to use the older SDK Tools.

Getting Help

To help us expedite a resolution to your issues, please consider these few points and use the template below and fill in your particulars. These points and the template below are meant to accelerate the process as much as possible. Why post your message and wait a day or so for someone to only have to ask one of the questions in the template when perhaps they could have replied with a suggestion or fix in that same amount of time? Why indeed.

• Getting the same error message as someone else does necessarily mean you have the same problem. If you suspect similar causes, post a link in your own, new thread where you have the details of your issue using the template below.
• Unlike the frameworks where browser is primarily important and Operating System is much less, with Sencha Cmd the operating system is very important.
• Sencha Cmd is designed to operate with Sencha frameworks - so please tell us which one you are using, e.g. Sencha Touch 2.1.1.
• The more specific you can be about what you did and what you saw, the quicker everyone reading will be able to get up to speed.

Please use the following template on threads when reporting issues. The next post on this thread shows what this will look like.

[U][B][COLOR=green]REQUIRED INFORMATION[/COLOR][/B][/U]


[B][U]Sencha Cmd version(s) tested:[/U][/B][LIST][*]Sencha Cmd 3.0.x[/LIST][B][U]Operating System:[/U][/B][LIST][*]________[*]Win7 Pro[/LIST][B][U]Framework used:[/U][/B][LIST][*]Sencha Touch 2.1.1[*]Ext JS 4.1.1a[/LIST][B][U]Description:[/U][/B][LIST][*]Describe the problem in greater detail here, summarizing the behavior.[/LIST][B][U]Steps to reproduce the problem:[/U][/B]

Please include [B]complete command lines[/B], be sure to mention the [B]current directory[/B] and finally a capture of the [B]console output[/B].

[CODE]
C:\MyCode\MyApp>sencha -debug app build production > log.txt
[/CODE]

Then post log.txt in a CODE block:

[CODE]
Sencha Cmd v3.0.2.288
...
[/CODE]

Also list any [B]customization[/B] to generated applications - file or folder renames or deletes; changes to config files. For example:

.sencha/app/sencha.cfg
[CODE]
    app.classpath=${app.dir}/mySrc
[/CODE]

[B][U]The result that was expected:[/U][/B][LIST][*] foo[*] bar[/LIST][B][U]The result that occurs instead:[/U][/B][LIST][*] bar[*] foo[/LIST][U][B][COLOR=green]HELPFUL INFORMATION[/COLOR][/B][/U]

[B][U]Screenshot or Video:[/U][/B][LIST][*]attached[/LIST][B]See this URL for live test case:[/B] http://


[B][U]Debugging already done:[/U][/B]

Many of the process steps provided by Sencha Cmd reside in generated code that lives in folders of your application (like .sencha/app/build.xml) or in scripts that ship in Sencha Cmd (CmdInstallDir/plugins/ext/current/plugin.xml or the "touch" folder instead of "ext").[LIST][*]None[/LIST][B][U]Possible fix:[/U][/B][LIST][*]not provided (perhaps there is a bug in a generated file or script)[/LIST]

[dongryphon]

REQUIRED INFORMATION


Sencha Cmd version(s) tested:

• Sencha Cmd 3.0.x

Operating System:

• ________
• Win7 Pro

Framework used:

• Sencha Touch 2.1.1
• Ext JS 4.1.1a

Description:

• Describe the problem in greater detail here, summarizing the behavior.

Steps to reproduce the problem:

Please include complete command lines, be sure to mention the current directory and finally a capture of the console output.

C:\MyCode\MyApp>sencha -debug app build production > log.txt

Then post log.txt in a CODE block:

Sencha Cmd v3.0.2.288
...

Also list any customization to generated applications - file or folder renames or deletes; changes to config files. For example:

.sencha/app/sencha.cfg

    app.classpath=${app.dir}/mySrc

The result that was expected:

• foo
• bar

The result that occurs instead:

• bar
• foo

HELPFUL INFORMATION

Screenshot or Video:

• attached

See this URL for live test case: http://


Debugging already done:

Many of the process steps provided by Sencha Cmd reside in generated code that lives in folders of your application (like .sencha/app/build.xml) or in scripts that ship in Sencha Cmd (CmdInstallDir/plugins/ext/current/plugin.xml or the "touch" folder instead of "ext").

• None

Possible fix:

• not provided (perhaps there is a bug in a generated file or script)