Configuration seems ok.
Was this application created with the 17-11 SDK, or updated from 17-8 for example?
The app was created before 17-11 SDK.
??? i cannot edit my post.
The app was created with whatever was up to date around 08.09.2017
Edit should be under "Actions", bottom left of your post.
Maybe the app is out of date, especially the grunt tasks which are in the /grunt folder of your app and some node-modules as well.
Did you update your app?
So its been some time and i have a small project (library) that i want to do, which contains a single viewcomponent and some configuration forms.
For this i purged most of my local innovation suite setup:
* reinstalled node vith nvm
* deleted my .m2 folder
* downloaded and installed the up to date SDK
* created two new projects (test app and lib)
and now i am running into the same issue again. No matter what i do i still get the unauthorized response from the user webservice
:9005/api/rx/application/user/$USER$:1 Failed to load resource: the server responded with a status of 401 (Unauthorized)
Last time i gave up and just disabled the uglyfy for the deployment so i could debug directly in my sandbox. But this is magnitudes slower than debugging with grunt.
Is there anything left that i could try to fix this?
1 of 1 people found this helpful
I think I had a similar problem because https is expected now.
I modified the files in my examples because of that (GitHub - lmame/Sample-Library-Public: Sample Library Public ).
Look at the file "connect.js' in grunt folder, my modification have a "// LMA" tag:
If memory serves I modify or added one line (seems I added it -> Modifying the project to use the 18.5.1 SDK and universal page, · lmame/Sample-Library-Public@5776c28 · GitHub ).
I think it is not useful here, I have not tested removing it
// LMA:: Adding protocol to debug on Aws instances. protocol: grunt.option('api-https') ? 'https' : 'http',
Then I use it in "open.js":
// LMA:: We need https to debug Qws instances. // url = 'http://' + grunt.option('host') + ':' + grunt.option('port'); protocol = grunt.option('api-https') ? 'https' : 'http', url = protocol + '://' + grunt.option('host') + ':' + grunt.option('port');
Then it should try to launch in https and your web browser should complain that the certificate is not correct or something so you will have to validate that it is ok to continue.
I think in Chrome you will have an "Advanced" link when Chrome complains and something like "Continue Anyway".
Thanks for the help!
I also noticed that "double grunting" is no longer necessary for testing libraries which is nice.
I am still using double grunt on some occasion though