not a valid path?

[Ricardh522]

I've used this tool with previous versions of WAB, but recently I get an error when specifying the path to the WAB root. I've tried all the combinations of root locations; drive letters; directory names; but nothing seems to work.

I've not looked at the source code yet to see if you are catching an error that I am not aware of but I'd like to go ahead and submit this request for a possible bug.

[gavinr]

What version of WAB are you using?

[Ricardh522]

The newest version 2.1. One thing I thought of that I did not try is to put double quotes around my path, but since there are no spaces in it, it was not something I thought of at the time. I am using windows 10.

[gavinr]

Hi Richard,

I just tested with the latest version of WAB and it seems to work fine for me. I'm on Windows 7. Can you please post the error message you're getting, or a screenshot?

Thanks!

[tomwayson]

Possible permissions issue?

[Ricardh522]

The initial attempts I made to use the tool were on my home PC where Node 4.4.7 is installed on the G drive separate from my operating system on C. In order to eliminate that as an issue for permission reasons, I am now doing the tests on my work pc which has only one drive C:.

What I did just now was extract the WAB zip file to generate the WebAppBuilderForArcGIS folder and moved it into a folder named WAB at the C:\ root. I get issues with the file path names being too long if the WebAppBuilderForArcGIS folder is located somewhere deeper in my path, like the user path. Next I create a src folder in the WAB folder as a sibling to the WebAppBuilderForArcGIS folder. I cd into the src folder and run the generator after first create a package.json file. The first time I ran the generator it created a jshint file, widget folder, and a theme folder, but did not generate the gruntfile nor did it run through the steps asking about the type of widget to create. It is not reproducing that behavior anymore now that I deleted the output created and am running the generator again.

I gotta get back on some tasks for reviewing docs here at the office, but I will be available to try this throughout the day.

Thanks,

Richard

[tomwayson]

Thanks for the detailed info. In the scenario you describe, you should enter c:\WAB\WebAppBuilderForArcGIS when prompted for the WAB root (not c:\\WAB\\WebAppBuilderForArcGIS

[Ricardh522]

This is the path to my web app builder directory as copied from the explorer path browser: C:\WAB\WebAppBuilderForArcGIS

[tomwayson]

Yes. So if you use that, does it work?

[tomwayson]

I've updated my comment above b/c it looks like GitHub's markdown was not showing the \\. Essentially, I think the double backslashes in your screenshot above are the problem.

[Ricardh522]

The above images show that the path with single backslash does not work.

I like your idea about it being a permissions issue. This laptop was recently updated to Windows 10, and since then I have updated my node.js to 4.4.7.

I've just ran the command prompt as admin and the results were the same.

The above image show that the default paths for the 2D widget is not the same as the default path for the 3d widget. It's probably not an issue itself but kinda weird.

[tomwayson]

I wonder if this is at all related to #64

Have you created any WAB apps yet?

What version of generator-esri-appbuilder-js do you have installed? You can run npm ls -g --depth=0 to see the version.

[Ricardh522]

That is exactly the problem. It works great now that I first create an app to generate the apps directory to satisfy the 'server/apps' string in the verify function of the generator.

[tomwayson]

Re-opening as a reminder until the fix for this lands in a release.

[gavinr]

This should be resolved in v2.1.1. Thanks for the report @Ricardh522!