We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
During Startup of VS2022 I get an error message from StartIsBack+ telling that something went wrong.
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Screenshots
Desktop (please complete the following information):
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Hi André
SP+ is simply reporting an error that it received from a web request. The error itself had to have come from amazonaws.com
The only place in SP+ that I would ever expect to see such an error is when opening a Developer News item, which I know you don’t use.
Does the error keep happening? Or is it just a one-off? What are you doing just before you see the error?
Yann
Sorry, something went wrong.
yes, it comes from the url https://vsstartpage.blob.core.windows.net/news/vs . Even when I turn Developer News off the extension still tries to read the URL.
Btw, can you please merge my PR #37 ?
Same error here in vs2022 with disabled 'developer news'. The error appears 1-2 times once I open Start+ in VS for the first time.
I use a different feed now to avoid this error
No branches or pull requests
Describe the bug
During Startup of VS2022 I get an error message from StartIsBack+ telling that something went wrong.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: