Results 1 to 9 of 9

Thread: Sencha Cmd v6.5.0.180 [ERR] Not a valid name/version ""

  1. #1
    Sencha User
    Join Date
    Apr 2017
    Posts
    2

    Default Sencha Cmd v6.5.0.180 [ERR] Not a valid name/version ""

    After upgrading to Sencha Cmd 6.5 I now receive the following error [ERR] Not a valid name/version ""

    sencha app build testing
    Sencha Cmd v6.5.0.180
    [INF] Processing Build Descriptor : default (testing environment)
    [ERR] Not a valid name/version ""



    Has anyone else seen this. What might I be missing? I can not find anything else on this issue.

    Thank you.

  2. #2
    Sencha User
    Join Date
    Feb 2013
    Location
    California
    Posts
    11,985

    Default

    From which version of Cmd were you upgrading? Which version of Ext JS are you using? Is this a standard app structure or have you moved some folders around to suit your requirements?

  3. #3
    Sencha User
    Join Date
    Apr 2017
    Posts
    2

    Default

    I was upgrading Sencha Cmd from 6.2.2.36 to 6.5.0.180. We are using Ext JS 6.0.1.250. I believe it is a standard project setup and not any custom setup.

    Would the Ext JS version need to be upgraded too?

  4. #4
    Sencha User
    Join Date
    Feb 2013
    Location
    California
    Posts
    11,985

    Default

    No it shouldn't need to. That's an unusual error though. One thing you can try is generating a fresh new application and migrating your code into it.

  5. #5
    Sencha Premium Member
    Join Date
    Aug 2015
    Posts
    14

    Default

    I just had this exact same error, but with a different version of Sench Cmd (v6.1.2.15). Turned out the problem was a trailing comma somewhere in the app.json.

  6. #6
    Sencha User
    Join Date
    Feb 2013
    Location
    California
    Posts
    11,985

    Default

    Normally that will trigger a Rhino parse warning, but it's certainly worth running your code through something like JSLint to eliminate that as a source of the problem.

  7. #7
    Sencha Premium Member
    Join Date
    Aug 2015
    Posts
    14

    Default

    I would expect a parse warning, but it doesn't for some reason... Out of curiosity I tested putting trailing commas in various places in the app.json file; in some cases it does just give a parse warning and then moves on, but if you put a trailing comma in the "requires" array this error occurs. In other places a null pointer exception occurs.

    The pattern seems to be that if you put a trailing comma in an array in the app.json, it will assume there's another element to come, so if it's expecting a string it will interpret it as "" (hence the error saying "" is not a valid name), and if it's expecting an object it will interpret it as null.

    Is this a peculiarity in the JSON standard that I'm not aware of, or is this a bug in Sencha Cmd's JSON parser? It's not a huge problem, but if it is a bug it would be nice if it was fixed to throw a more helpful error message or warning.

  8. #8
    Sencha User
    Join Date
    Feb 2013
    Location
    California
    Posts
    11,985

    Default

    I found a bug report (SDKTOOLS-1432) for the trailing comma issue in app.json. The issue was at least partially fixed, but it seems trailing commas in some parts of the file don't report errors to Cmd, limiting what we can do. It seems that the 'requires' block is one of those.

  9. #9
    Sencha Premium User
    Join Date
    Jan 2014
    Posts
    9

    Default Trailing comma in app.json "requires": block

    Quote Originally Posted by Gary Schlosberg View Post
    it seems trailing commas in some parts of the file don't report errors to Cmd, limiting what we can do. It seems that the 'requires' block is one of those.
    Yes, I had a trailing comma after the last package in the 'requires' block and Cmd 7.0.0 threw this error. Thank you for this comment -- saved me from starting over with a fresh app.

Similar Threads

  1. sencha command throws error "... not a valid SDK directory ..."
    By Dierk in forum Sencha Touch 2.x: Q&A
    Replies: 2
    Last Post: 1 May 2013, 3:21 AM
  2. Replies: 14
    Last Post: 7 Jan 2013, 9:41 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •