Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SPGo no go after VS Code March update #142

Closed
ghost opened this issue Apr 1, 2021 · 13 comments
Closed

SPGo no go after VS Code March update #142

ghost opened this issue Apr 1, 2021 · 13 comments
Assignees
Labels

Comments

@ghost
Copy link

ghost commented Apr 1, 2021

** SPGo no go after VS Code march update **

  • **I'm submitting an issue with the SPGo plugin **
    Since I applied the March update for VS Code I can no longer sync with SharePoint.
    Spins for ever if it even starts.
    I've researched rolling back VS Code to version 1.54(Feb) from 1.55 (March).
    An exhaustive search of the interweb reveals no clues or shows others with the same issue.
    I've been developing all day with no issues.

Thanks :)

@ghost ghost added the bug label Apr 1, 2021
@ghost ghost assigned chrishasz Apr 1, 2021
@ghost
Copy link
Author

ghost commented Apr 5, 2021

Anyone else have this issue?

@ghost
Copy link
Author

ghost commented Apr 5, 2021

As a form of confirmation, if for only me :), I uninstalled 1.55 and reinstalled 1.54 and now I'm good to go.

@chrishasz
Copy link
Owner

Hello @billr-stcu

Sorry you are having issues with SPGo and VSCode 1.55. I'm out of town right now, but I will take a look at this as soon as I am back.

In the meantime, did you see any errors in the log/output window when SPGo failed to load?

@ghost
Copy link
Author

ghost commented Apr 6, 2021

@chrishasz sorry no.
Was in a rush to get it working, so uninstalled and reinstalled the older version clearing the logs.
I'm sure the logs would have been useful.
Just in case I will look to see if perhaps they remained behind.
It I do find them, I will be sure to add them to this thread.

Thanks

@ghost
Copy link
Author

ghost commented Apr 13, 2021

@chrishasz hi.
did anyone else experience this issue?
thx

@ianoel230982
Copy link

I've just upgraded to v1.56 April 2021 update.
In my extension output in the terminal i now get the below message after i input my credentials

================================ ERROR ================================
[13/05/2021, 10:21:10] 401 - undefined
[13/05/2021, 10:21:10] Error Detail:
[13/05/2021, 10:21:10] ----------------------
[13/05/2021, 10:21:10] StatusCodeError: 401 - undefined
[13/05/2021, 10:21:10] ===============================================================================

I've looked in the vs code dev tools and there are no errors at point when i hit the 'enter' key.

I can't provide any more info at this stage and i'm going to have to regress to previous version of vs code ( a colleague of mine also had the same issue too) otherwise i won't be able to work :-)

@chrishasz
Copy link
Owner

All- I just published SPGo 1.7.2 to the Marketplace and one of the updates was to bump the vscode engine.

Can you check and see if this issue (142) is resolved?

@stephanerosa
Copy link

Hello,

I have VSCode 1.56.2 & SPGo 1.7.2 but there is no way I can authenticate to my Sharepoint 2013 on-premise. I tried Digest or NTLM with either DOMAIN\USER or email, or USER@domain, etc.

I can't seem to find any log files whatsoever. Where would they be ?

Any SPGo function indefinitely asks for credentials, and/or hangs forever. I think last time it worked was indeed before a VSCode upgrade.

@ianoel230982
Copy link

@stephanerosa if you check out the linked issue, i think you'll find the resolution to your problem. Head towards the bottom of the comments and scroll up. It's probably to do with the proxy settings for extensions #73
Hope that helps.

@stephanerosa
Copy link

@stephanerosa if you check out the linked issue, i think you'll find the resolution to your problem. Head towards the bottom of the comments and scroll up. It's probably to do with the proxy settings for extensions #73
Hope that helps.

Awesome, that worked. I guess this issue could be closed then.
Thank you very much.

@chrishasz
Copy link
Owner

Thank you, @ianoel230982!

@ghost
Copy link
Author

ghost commented May 20, 2021

Worked for me too.
Sorry for the lengthy respond. Lots of work, blah blah blah :)

Made the proxy setting change to Off and synching files is working.

Thanks all for drilling into this.

@ghost ghost closed this as completed May 20, 2021
@ghost
Copy link
Author

ghost commented May 20, 2021

Closing issue

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants