Results 1 to 5 of 5

Thread: SA can't understand a remote folder in packages.

    You found a bug! We've classified it as DSGNR-7266 . 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
    Join Date
    Mar 2013

    Default SA can't understand a remote folder in packages.


    Architect Build tested:
    Project Type:
    • ExtJS 6.x Classic

    SA can't recognize a new packages directory structure when using with local repository.
    From Cmd 6.x, packages has remote and local folder. But, SA seems treat remote folder as a package.

    I think SA want to check packages that is a properly AUX. But in some case, User will add packages that is NOT a AUX. In fact, SA check a architect property in package.json, this property should be only used with a aux package.
    SA should handle such use case.

    Steps to reproduce the problem:
    • Create a new Ext JS 6.x
    • Modify requires in app.json to use a remote package with local repository.
    • (Cmd will copy the required remote package automatically to /packages/remote direcotry)
    • Quit Project
    • Reopen Project
    The result that was expected:
    • No errors should be occurred.
    The result that occurs instead:
    • Following error log displayed.
    PHP Code:
    Failed to load package (path/to/project)/packages/remote this package is 
    missing the 
    .sencha folderwhich means it was not generated with Sencha Cmd and will 
    therefore not be able to used in the build process
    Please use an updated version 
    properly generated with Sencha Cmd


    Possible fix:
    • Don't use remote folder as a package.
    Operating System:
    • Win7 Pro

  2. #2
    Sencha Premium Member
    Join Date
    Mar 2013


  3. #3
    Sencha User
    Join Date
    Sep 2014
    Central Europe



    Thanks for the report. We will look into it.
    Does it blocks you in building the project / any other problems or is the problem just the error message.


  4. #4


    Have you generated the package using
    sencha generate package somepackage
    sencha package build
    Then added the .pkg file (in your workspace build folder) into your new project's workspace using
    sencha package add somepackage.pkg
    As this will put the package into the remote folder. Only the original workspace where you create the package will it be in local. I've been doing a few of these package recently so have seen similar errors.
    I am also using Sencha Architect 3.5 with custom packages.
    Last edited by richard.styles; 17 Jul 2016 at 12:35 PM. Reason: formatting

  5. #5


    Thanks for the report! I have opened a bug in our bug tracker.

Similar Threads

  1. Maintaining a remote repository for packages
    By Fredric Berling in forum Sencha Cmd
    Replies: 9
    Last Post: 7 Mar 2017, 11:33 AM
  2. Can't understand app folder structure in extjs app
    By bluesky100 in forum Ext JS 6.x Q&A
    Replies: 5
    Last Post: 31 May 2016, 11:50 PM
  3. Replies: 1
    Last Post: 30 Apr 2014, 6:17 PM
  4. How to change theme folder name in packages folder
    By isolanet in forum Sencha Architect 3.x: Q&A
    Replies: 1
    Last Post: 4 Feb 2014, 10:10 AM
  5. Parent folder icon changed on deletion of child folder
    By sachin sachdeva in forum Ext 3.x: Help & Discussion
    Replies: 0
    Last Post: 11 Oct 2010, 9:47 PM

Posting Permissions

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