SA can't understand a remote folder in packages.

[kobayashi.masashi]

REQUIRED INFORMATION

Architect Build tested:

• 3.2.1.348

Project Type:

• ExtJS 6.x Classic

Description:

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.

Failed to load package (path/to/project)/packages/remote - this package is 
missing the .sencha folder. which 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. 

HELPFUL INFORMATION

Possible fix:

• Don't use remote folder as a package.

Operating System:

• Win7 Pro

[kobayashi.masashi]

[petr.vecera]

Hi

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.

Thanks

[richard.styles]

Have you generated the package using

sencha generate package somepackage

then

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.

[alex.volfson]

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