-
Notifications
You must be signed in to change notification settings - Fork 12
[bug] JS error when trying to open console #221
Comments
I have encountered the same one using a comet and a planet later that day. I have Windows 10. Port Version: 1.9.0 |
I'm the person that encountered the issue in the image. Also encountered this on Windows 10. To give a bit more context, this happened right after I updated Port to 1.9. Here's my initial mail to the support team before being diagnosed as a bug and the issue was created: (502) All mail _ hermescorp@protonmail.com _ Proton Mail.pdf |
We pushed out a patch version that resolves a lot of the issues people were experiencing with the last release. Can you give 1.9.1 a spin and let me know if you're still experiencing this? |
Hmm strange that some are working and others aren't. Can you try exporting the problematic ships and then reimporting them? This will help me determine if this is an issue related to Port's configuration vs an issue on the Urbit side. Steps for that are:
If you need any help doing this, feel free to message me on network at |
@latterbolden I've followed this process. This might have been because maybe I didn't set up the directory location correctly. Second time worked and I can open landscape but my ship cannot connect at all now. Still can't use any other app. |
After months, I am still encountering this problem. I got a new device running windows 11 (eww I know), "tarballed" my ship from my other computer and migrated it to the new device and while port seems more fast and all apps open, it seems like the ship has been stuck in August 2022 and hasn't been able to connect to the network and update messages since. The JS error keeps popping up when closing Port so I guess the issue is not merely a JS bug on the application layer but might have to do with my ship itself. I will still have to try booting the ship without port to check if that is the case. |
*Bug Description
JS error when trying to open the terminal
To Reproduce
Steps to reproduce the behavior:
Expected Behavior
Terminal to open.
Screenshots
Environment:
The text was updated successfully, but these errors were encountered: