-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Sharing link to sandbox does not have any code updated #8689
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
Comments
The fork is also not updated. So basically all the work gets lost unless you manually copy/paste it to a new fork. |
Ha, and then after forking I get Lovely. You guys easily have the best environment, BUT IT DOESN'T SAVE PROPERLY! |
Every damn time I use this site... |
Same here... |
Hmm, so if I understand correctly, if you share a link to a sandbox with someone else, and they start editing it, they get an error back and the code is not saved? I'm looking to repro & fix this. |
I'm also seeing this in some Next.js devboxes lately... 🤔 Example devbox: https://codesandbox.io/p/devbox/fast-tree-x7zpn2?workspaceId=ws_GfAuHrswXyA1DoeSwsjjjz |
Making it public did not resolve my issue - but the fact that the share button doesn't imply making it public is crazy in itself. |
Interesting... I will take a look at the
We don't automatically make it public/unlisted because you can still share it with members in your workspace. This is the same behavior/UX as Google Docs/Drive, Figma and Notion so it's not that uncommon. |
@CompuIves here's some reproduction steps:
Note: This only applies for my case - maybe there are multiple cases, since making the devbox public did not help with what @Nantris was experiencing. |
I think this must be a race condition, I've been trying to repro it but couldn't yet. I've also asked the team to see if they could repro it. |
I get this too but only when I'm using Chrome Beta. If I use the standard version of Chrome I have no issues. |
Oh! That's a very good indication. Perhaps there is a new Chrome security change that's only enabled for x% of browsers. I have seen this before (with partial cookies) where some Chrome instances had it enabled and others didn't, to do a gradual rollout. |
In our case, I've seen this intermittently since months, on regular stable Chrome versions. (didn't try other browsers) |
@CompuIves I have seen this issue for many months before finally filing an issue. |
Another example sandbox which shows the If there's anything that I can do to debug or make these reports more usable or actionable, then let me know - happy to help! |
Maybe helpful note, but I do always get this error on |
I do confirm that the error |
🐛 bug report
Preflight Checklist
adheres to.
to file, without success.
Description of the problem
Sharing link to sandbox does not have any code updated.
How has this issue affected you? What are you trying to accomplish?
This is frequently happening and then I think, "Okay I guess I have to fork it?" and it tells me I already own it... All the files are saved.
To Reproduce
Use CodeSandbox, ever, in any capacity, in my experience.
Link to sandbox: link (optional)
Your Environment
The text was updated successfully, but these errors were encountered: