Results 1 to 5 of 5

Thread: CMD v4.0.0.203: app.json not found (null pointer exception)

  1. #1

    Default CMD v4.0.0.203: app.json not found (null pointer exception)

    Hi there,

    I have a new Sencha Touch 2.3 application and want to update the bootstrap.json file, so I use 'sencha app refresh'. This leads to a NullPointerException because the file 'app.json' was not found:

    Bildschirmfoto vom 2013-10-06 11:22:09.png

    However, the file /opt/bitnami/apache2/htdocs/yimm_sencha/app.json exists!
    Is this a bug in the latest cmd version?

    Regards,
    Peter

  2. #2
    Sencha User slemmon's Avatar
    Join Date
    Mar 2009
    Location
    Boise, ID
    Posts
    6,165

    Default

    Can you do the following command:
    "sencha -debug app refresh > path/to/debug.log"
    and post back the full debug log?

  3. #3

    Default

    Siemmon,

    I have attached the debug file.

    Thanks a lot for your help!
    Attached Files Attached Files

  4. #4

    Default

    Finally I found the reason for the nullpointer exception, it was one single comma in app.json!

    I have specified a js file to be included like that:

    Code:
    "js": [
            {
                "path": "phonegap.js",
                "remote": true
            },
            {
                "path": "touch/sencha-touch.js",
                "x-bootstrap": true
            },
            {
                "path": "bootstrap.js",
                "x-bootstrap": true
            },
            {
                "path": "app.js",
                "bundle": true,  /
                "update": "delta"
            },
            {
                "path": "app/js/yimm.js",
                "update": "delta"
            },
        ],
    The comma (marked red) after the closing bracket of the import of yimm.js seems to be wrong. Simply removing the comma solved the issue...

  5. #5
    Sencha User slemmon's Avatar
    Join Date
    Mar 2009
    Location
    Boise, ID
    Posts
    6,165

    Default

    I see. Thanks for sharing the fix! I'll take this to the Cmd engineer and see if there's a better way for us to review the file for parse errors and raise better warnings going forward.

Posting Permissions

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