-
Notifications
You must be signed in to change notification settings - Fork 22
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
Error when opening the app #17
Comments
I still need help on this |
I have the same issue running on the latest Ventura beta. I think this might be the reason for the error. What macOS do you use? |
I tried on Monterrey don't exactly know what version but for Ventura dev beta 3 it doesn’t work on my Mac at all I’m using an MBP 14inch M1 Pro |
Same error in latest stable macOS (Ventura). |
@Becivells did you get this to work? Specs: up-to-date Ventura, m1 air Excuted, seemed to run but it stopped almost immediatly with this error: guess this doesn't work on Mac anymore. |
and an error:
Normally I have installed Python myself but I see that its now using the system one again.
although I think its just a security issue |
I wish this wasn’t so much of an ongoing problem trying to use my switch with it is non existent I’ve just gone too using an old Mac and doing it that way. |
Oh! forget my errors, the alt version seems to run just fine! now checking if it actually works as well |
I'm going to document this a bit for others.
I never ran things as |
In the meantime, if anyone else can't get it to work, I found this wonderful workaround for sending payloads through Google Chrome: |
This SAVED me 5 months later, god bless, this is the only solution that worked for me. |
Just thank you. It's been so long since this has gotten a reply. |
Still having the same issues as above, changed the settings for the relevant files in the MacOS folder to use iTerm, but still receiving the "session ended very soon after starting" error. Used the "alt" key to start the app. Any advice? Translated Report (Full Report Below)Process: fusee-interfacee-tk-bin [5383] Date/Time: 2023-05-13 02:26:36.5518 -0400 Sleep/Wake UUID: 42797673-B9BA-4E77-9C0C-E52B5A0B00F6 Time Awake Since Boot: 27000 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Termination Reason: Namespace SIGNAL, Code 4 Illegal instruction: 4 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread Thread 1:: com.apple.rosetta.exceptionserver Thread 2:: Dispatch queue: MTLLibraryData queue Thread 3: Thread 4: Thread 5: Thread 6: Thread 7:: com.apple.NSEventThread Thread 0 crashed with X86 Thread State (64-bit): Binary Images: External Modification Summary: VM Region Summary:
REGION TYPE SIZE COUNT (non-coalesced) |
"“fusee-interfacee-tk-bin” can’t be opened because (null) is not allowed to open documents in Terminal." I get this error when opening fusee
The text was updated successfully, but these errors were encountered: