You found a bug! We've classified it as SDKTOOLS-498 . We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
  1. #1
    Sencha Premium Member EPV's Avatar
    Join Date
    Dec 2010
    Location
    Sweden
    Posts
    175
    Vote Rating
    13
    EPV will become famous soon enough

      0  

    Default Sencha Cmd v3.1.1.274 - debug possibilities

    Sencha Cmd v3.1.1.274 - debug possibilities


    I'm moving to 3.1.1.274 from 3.1.0.256 where building production worked fine. Now I get:
    Code:
    [ERR] C2000: Rhino Parse Error (missing name after . operator => if (!NS.view.public) NS.view.public = {};) -- null:7778
    Building test works fine ...

    My question is if there's any way of finding where it goes wrong, like in a log file or something.

    The thing is that the application is really big and its €#"%&/€ debugging it.

    Thanks / E

  2. #2
    Sencha - Senior Forum Manager mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    37,065
    Vote Rating
    852
    mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute

      0  

    Default


    You can use the -d flag to give you more info but I double for this error you will get much more than what it gives you.
    Mitchell Simoens @SenchaMitch
    Sencha Inc, Senior Forum Manager
    ________________
    Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
    https://github.com/mitchellsimoens

    Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/

    Need more help with your app? Hire Sencha Services services@sencha.com

    Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!

    When posting code, please use BBCode's CODE tags.

  3. #3
    Sencha Premium Member EPV's Avatar
    Join Date
    Dec 2010
    Location
    Sweden
    Posts
    175
    Vote Rating
    13
    EPV will become famous soon enough

      0  

    Default


    I've tested -d but that doesn't give me any more info unfortunately.

    The error is direct after the line:
    Code:
    [INF] Compressing data with YuiJavascriptCompressor
    I should be possible to somehow find where the error happens, shouldn't it?

    What does "-- null:7778" means?

    I would like to have the concatenated file ...

    Code:
    [INF] Building optimized concatenated output..
    .. and the line number where the error throws.

    Thanks / E

  4. #4
    Ext JS Premium Member
    Join Date
    Jan 2011
    Location
    NORWAY
    Posts
    106
    Vote Rating
    1
    frankbolviken is on a distinguished road

      0  

    Default


    I have the exact same issue, can't build the application because of this error.. with no explaination of where it happens or anything. Enabled -d, and it just gave me the stacktrace, but still no info on where etc.

    Quote Originally Posted by EPV View Post
    I've tested -d but that doesn't give me any more info unfortunately.

    The error is direct after the line:
    Code:
    [INF] Compressing data with YuiJavascriptCompressor
    I should be possible to somehow find where the error happens, shouldn't it?

    What does "-- null:7778" means?

    I would like to have the concatenated file ...

    Code:
    [INF] Building optimized concatenated output..
    .. and the line number where the error throws.

    Thanks / E

  5. #5
    Sencha Premium Member EPV's Avatar
    Join Date
    Dec 2010
    Location
    Sweden
    Posts
    175
    Vote Rating
    13
    EPV will become famous soon enough

      0  

    Default


    Our problem was finally solved by replacing "public" from the namspace "NS.view.public.ABC". It seems that JavaScript reserved words cannot be used in namespaces ...

    https://developer.mozilla.org/en-US/...Reserved_Words

    We also hade problems with "export" in another project (which also build perfectly in previous versions of CMD).

    The example in the link above states that it's ok to use reserved words when there not identifiers (like "a.import"). Shouldn't it be like that in Sencha Cmd?

    Also, there should be much better error when something goes wrong in a build.

    / E

  6. #6
    Sencha User
    Join Date
    Oct 2007
    Posts
    5
    Vote Rating
    0
    JoSsiF is on a distinguished road

      0  

    Default


    Thanks very much! This solved my problem, too.

    JoSsiF

  7. #7
    Sencha - Ext JS Dev Team dongryphon's Avatar
    Join Date
    Jul 2009
    Posts
    1,346
    Vote Rating
    134
    dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all

      0  

    Default


    Thanks for the report! I have opened a bug in our bug tracker to see about improving the error messages in this case.

  8. #8
    Sencha - Ext JS Dev Team dongryphon's Avatar
    Join Date
    Jul 2009
    Posts
    1,346
    Vote Rating
    134
    dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all dongryphon is a name known to all

      0  

    Default


    Internal to Cmd we use the Rhino JavaScript parser (just like YUI) and that is what gets cranky about use of JavaScript's reserved words. We have not changed that in recent releases so I don't know how it could have worked previously. These errors usually show up when "debugger" statements get left in the code.
    Don Griffin
    Ext JS Development Team Lead

    Check the docs. Learn how to (properly) report a framework issue and a Sencha Cmd issue

    "Use the source, Luke!"