-
Notifications
You must be signed in to change notification settings - Fork 13
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
WLJS on Mac M1 install buggy #61
Comments
Hi! Sorry to hear that. I would like to ask to share the startup log file
It might contain some private information, please consider that. |
and, where did it stuck, by the way? |
By the experiment I have found
The only solution for Wolfram Engine to work on M1 I found brew install --cask wolfram-engine |
Ok. Soon, we will release the client app that takes care about all this installation hassle |
Just echoing; I tried today and got "“WLJS Notebook” is damaged and can’t be opened. You should move it to the Trash." I'm on an M3 Pro. |
Hm. I recompiled it again using fresh Electron version (could be a problem with Electron version & OSX). |
Thanks. I had the same problem, but then I tried the following:
And I got further. Maybe 0.7.0 would have opened also had I done this. (Note that the normal trick of control-clicking on the App and picking 'Open' didn't work in this case.) Anyway, wow I can load the nine sample *.wln files, although I regularly get the |
I am having the same problem ""“WLJS Notebook” is damaged and can’t be opened. You should move it to the Trash.", also on M3 with macOS Sonoma on WL 13.3 |
Hi @aclysma , Could you please try a universal build for OSX? On Electrons troubleshooting forums, people blame the latest stable Sonoma release. I am actually on Sonoma Beta for similar reasons, however, hope this fix above will help you without taking a risk on using beta-channel. |
FWIW, this one worked better for me. I still get the "could not verify it was free of malware" message, but control-clicking on the app works. Loading documents: I still got a series of popups the first time I loaded a doc, but loading more documents after that point was smooth. |
Moving package to Trash and reinstalling didn't change anything, it still sticks at above. |
0.7.2 was able to launch, thanks! My experience was similar to what @tunesmith described. |
When I checked the file I see this --
I had installed Mathematica 14 and there is a conflict with the Wolfram Engine. is there a way to reverse everything and start from scratch - pick which wolframengine to use? |
Sure! Please, remove |
Ok that worked! Now, I can play around.Thx!On Jan 20, 2024, at 10:47 AM, Kirill Vasin ***@***.***> wrote:
I had installed Mathematica 14 and there is a conflict with the Wolfram Engine. is there a way to reverse everything and start from scratch - pick which wolframengine to use?
Sure! Please, remove configuration.ini in AppData folder (./conf/wljs-frontend) and restart
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Ok, still a problem. Once I pointed to the wolframscript in /usr/local/bin/wolframscript, the program launched and I was able to view all example files. But I was not able to evaluate any new wolfram expression - nothing happens. |
Do you have a green line on the left side between the sidebar and notebook? Also in logs, when you start a kernel from the menu it shows the kernel status (you can attach a screenshot or just text from logs..) Due to buggy licensing of Wolfram Engine, sometimes Wolfram Engine blocks second kernel to be launched... |
ok, I re-activated the free Wolfram Engine (13.3) and pointed to it instead of the MM v14 now it works. Thx! |
Still not fixed |
Solutions are listed in docs |
Fixed in signed release |
Hi, your product looks promising, but I just couldn't get it installed (Desktop version) on my Mac M1. Tried multiple times over a period of months, but no go.
The text was updated successfully, but these errors were encountered: