-
Notifications
You must be signed in to change notification settings - Fork 1k
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
StackBlitz fails to create new GitHub repo for new project #959
Comments
I noticed when this happened a my browser blocked a pop up and I had to allow that. Then the process continued and I was a able to move forward |
@Wrensummerset Tried it again just now, and didn't get any prompt (Chrome 79.0.3945.117 on macOS). I also tried manually specifying allowing popups to stackblitz.io, still no dice. :\ Still getting the same errors in my console as well. At this point there's still numerous open issues with the GitHub integration from the past year, which really sucks for my hopes of having this fixed. I'm hoping at some point these get fixed, but in the meantime I've opted to using Visual Studio Online. |
+1 |
I love stackblits and its awesome but this feature is important. For now, I have found codesandbox.io that has the github sync working. Hope stackblitz will fix this sometime. |
+1 |
Hey all- this issue sometimes is caused by chrome extensions that interfere with requests (i.e. adblockers). Can y'all try turning off all extensions and lmk if that resolves the issue? Would also appreciate links to the projects that are showing these errors so I can debug on our end |
@EricSimons - Thanks for getting back to us! I'm now able to login and accept the OAuth2 flow, with and without my Chrome extensions active. However, when clicking "Connect Repo" and clicking "Create Repo & Push", a blank repository is created in GitHub, but no source code is ever pushed. I'm still able to edit files and click "Commit" at the top, but doing so still doesn't push any code to GitHub. I tried checking "make this repository private" and that had the same results: a blank private repository is created, but no commits make it over. Some examples: https://stackblitz.com/edit/react-sbcrj8 https://stackblitz.com/edit/angular-fm1w9t https://stackblitz.com/edit/rxjs-zexqpz Let me know if you need any more information for debugging (network traces, etc) |
I'm having the same 401 issue and I've tried turning off all extensions in both chrome and edge to no avail. If I try to open old projects that were created in Stackblitz, it would get stuck on Initializing GIT Repository. Here is one of those project https://github.com/bzhao16834/github-8udwbr |
For what it's worth, I've succeeded creating a new repo in Github from Stackblitz by doing the following steps :
I think the issue is that when you login and associate your Stackblitz and Github account, it does just ask permission for personal info. Hope this will help |
Had the same issue. GitHub OAuth token did not have proper scope, so removed it and logged out of Stackblitz, logging back in using "Connect Repository" button (to ensure it asks for proper OAuth scopes this time). Still had an issue with Safari blocking pop ups (so had to manually allow popups stackblitz.com, no prompt was given), and then tried again, issue resolved. |
Works thanks |
This issue is now resolved in our new VS Code editor! Full writeup in Github issue #2473 |
For me it was enough to disable uBlock origin on stackblitz domain |
Initially when creating a new project, I was having issues with StackBlitz syncing new changes to its newly created GitHub repo. I removed StackBlitz as a Trusted OAuth App in GitHub (https://github.com/settings/applications -> Click ... next to StackBlitz -> Revoke), and now when I go to create a new repo for a new project, the GitHub authorization flat-out fails with a 401, even after reauthenticating myself with StackBlitz. See repro steps and video below.
Reproduction Steps:
Video: https://i.imgur.com/iUZryxz.mp4
Expected result: StackBlitz creates a GitHub repo with the project code
Actual result: StackBlitz fails to create a repo, citing bad credentials.
The text was updated successfully, but these errors were encountered: