Codesandbox-client: "An unrecoverable sandbox error" and phantom UI when importing from private Repo

Created on 6 Jan 2019  ·  10Comments  ·  Source: codesandbox/codesandbox-client

🐛 bug report

Description of the problem

When trying to import a private GitHub repo, receive a "An unrecoverable sandbox error occurred. :-( Try refreshing the page." error, and browser panel refreshes to contain duplicate of Codesandbox UI (see below).

screenshot 2019-01-06 at 10 42 07 pm

How has this issue affected you? What are you trying to accomplish?

I can't import private repos to edit projects.

Your Environment

| Software | Name/Version|
| ---------------- | ---------- |
| Сodesandbox | PROD-1546812717-fd56384b
| Browser | Google Chrome OS/Version 70.0.3538.110 (Official Build) (64-bit)
| Operating System | Google Chrome OS/Version 70.0.3538.110 (Official Build) (64-bit)

All 10 comments

Hey @durkinio , that's because we don't support private server sandboxes for now (mainly because the preview is publicly accessible, which is a concern for something that should be private). But you're right, the current behavior is far from ideal, we should probably show a warning explaining the situation.

Closing this - feature is working as expected/by design.

wasted hours cause of this.. :(

please disable the fork button when someone makes a private sandbox.

I am facing the same issue now. what is the solution please ?
Thanks in advance!

did you lock the sandbox? if you make it private it won't load anymore..
hope this helps

On Thu, 4 Apr 2019 at 09:28, Muhammed-Shaarawy notifications@github.com
wrote:

I am facing the same issue now. what is the solution please ?
Thanks in advance!


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/CompuIves/codesandbox-client/issues/1431#issuecomment-479783114,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AK1dV-b4fsMEMQfQmzaWL-lRfEGWVr2Oks5vdamcgaJpZM4ZypVW
.

--
Leclercq Dominiek
D1K consultancy

did you lock the sandbox? if you make it private it won't load anymore.. hope this helps

On Thu, 4 Apr 2019 at 09:28, Muhammed-Shaarawy @.*> wrote: I am facing the same issue now. what is the solution please ? Thanks in advance! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1431 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AK1dV-b4fsMEMQfQmzaWL-lRfEGWVr2Oks5vdamcgaJpZM4ZypVW .
-- Leclercq Dominiek D1K consultancy

I just import repositories from a private GitHub repositories account after subscribing and become a CodeSandbox Patron.
I imported 2 repositories, one using React JavaScript which works and loads fine, the other repository using React Typescript which never loaded.

I do not know about locking the sandbox or make it private. i just did that.
What do you think?

Thank you @domi1kenobi

If your sandbox was made private you would see a locker on the sandbox in
the sandbox overview. That was the issue I had. Because it's private it
won't load due to access rights.

On Fri, 5 Apr 2019, 05:25 Muhammed-Shaarawy, notifications@github.com
wrote:

did you lock the sandbox? if you make it private it won't load anymore..
hope this helps
… <#m_9189620184660119231_>
On Thu, 4 Apr 2019 at 09:28, Muhammed-Shaarawy @.*> wrote: I am
facing the same issue now. what is the solution please ? Thanks in advance!
— You are receiving this because you commented. Reply to this email
directly, view it on GitHub <#1431 (comment)
https://github.com/CompuIves/codesandbox-client/issues/1431#issuecomment-479783114>,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AK1dV-b4fsMEMQfQmzaWL-lRfEGWVr2Oks5vdamcgaJpZM4ZypVW
.
-- Leclercq Dominiek D1K consultancy

I just import repositories from a private GitHub repositories account
after subscribing and become a CodeSandbox Patron.
I imported 2 repositories, one using React JavaScript which works and
loads fine, the other repository using React Typescript which never loaded.

I do not know about locking the sandbox or make it private. i just did
that.
What do you think?

Thank you @domi1kenobi https://github.com/domi1kenobi


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CompuIves/codesandbox-client/issues/1431#issuecomment-480136166,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AK1dV0HDHpPe8cjANdGj202hZ-M0sbxDks5vdsIngaJpZM4ZypVW
.

I was totally not expecting this to be the issue. Maybe a more intuitive error would have prevented me to think it was an unexpected error from the sandbox.

So the solution, for now, is to not use private sandbox with the server?

What I do is unlock only the ones I'm testing and lock them again
afterwards.

On Fri, 21 Jun 2019 at 11:00, Tomás Francisco notifications@github.com
wrote:

I was totally not expecting this to be the issue. Maybe a more intuitive
error would have prevented me to think it was an unexpected error from the
sandbox.

So the solution, for now, is to not use private sandbox with the server?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/codesandbox/codesandbox-client/issues/1431?email_source=notifications&email_token=ACWV2V4IJARTDRYKWQ44Q73P3SKENA5CNFSM4GOKSVLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYH4RNQ#issuecomment-504350902,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACWV2VYG2Z7IEXXI3EUJHPTP3SKENANCNFSM4GOKSVLA
.

--
Leclercq Dominiek
D1K consultancy

Was this page helpful?
0 / 5 - 0 ratings