WLJS on Mac M1 install buggy

[gganapat]

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.

[JerryI]

Hi! Sorry to hear that.
Actually I am also using it on M1 machine and had some issues with the latest WL update.

I would like to ask to share the startup log file

You can find it using "File" (or top bar menu for Mac users) menu, then click on "Locate AppData" (installation directory), where in the root directory there is a file 2MinutesLog.txt. Please send it to us.

It might contain some private information, please consider that.

[JerryI]

and, where did it stuck, by the way?

[JerryI]

By the experiment I have found

• M1 + WL 13.3 = crash (on FunctionCompile used in HTTP Server)
• M1 + WL 13.2 = download manager return Pointer = Null
• M1 + WL 13.1 = crash
• M1 + WL. 13.01 = download manager return Pointer = Null

The only solution for Wolfram Engine to work on M1 I found

brew install --cask wolfram-engine    

[JerryI]

Ok. Soon, we will release the client app that takes care about all this installation hassle

[tunesmith]

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.

[JerryI]

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).
Could you, please, try this version ?

[tunesmith]

Thanks. I had the same problem, but then I tried the following:

MacBook-Pro-2:/Applications$ xattr WLJS\ Notebook.app/
com.apple.provenance
com.apple.quarantine
MacBook-Pro-2:/Applications$ xattr -d 'com.apple.quarantine' WLJS\ Notebook.app/
MacBook-Pro-2:/Applications$ open WLJS\ Notebook.app/

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 WS connection to kernel server is lost and [object Close Event] red popups, basically every time I click on a new file or on the window.

[JerryI]

Thanks. I had the same problem, but then I tried the following:

MacBook-Pro-2:/Applications$ xattr WLJS\ Notebook.app/
com.apple.provenance
com.apple.quarantine
MacBook-Pro-2:/Applications$ xattr -d 'com.apple.quarantine' WLJS\ Notebook.app/
MacBook-Pro-2:/Applications$ open WLJS\ Notebook.app/

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 WS connection to kernel server is lost and [object Close Event] red popups, basically every time I click on a new file or on the window.

I am still shocked how different things can go within a single platform even using Electron (not QT or something).
Hope an updated version will open properly for OSX users. The red message is kinda okaish if examples with Dynamics work properly.

A restart of a Kernel might help. Then a green line should appear on the left side of the notebook

Anyway, we are rewriting frontend from scratch in dev-branch now to get rid architectural workarounds and instability.

[aclysma]

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

[JerryI]

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 ,
One more attempt.

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.

[tunesmith]

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.

[gganapat]

I tried the above and initially got the message that the WolframEngine couldn't be found and asked me to locate it, which I did. Then it started and froze at this point

[gganapat]

Moving package to Trash and reinstalling didn't change anything, it still sticks at above.

[aclysma]

0.7.2 was able to launch, thanks! My experience was similar to what @tunesmith described.

[gganapat]

Hi! Sorry to hear that. Actually I am also using it on M1 machine and had some issues with the latest WL update.

I would like to ask to share the startup log file

You can find it using "File" (or top bar menu for Mac users) menu, then click on "Locate AppData" (installation directory), where in the root directory there is a file 2MinutesLog.txt. Please send it to us.

It might contain some private information, please consider that.

When I checked the file I see this --

checking the installation folder...
/Users/gani/Library/Application Support/wljs-frontend

Current version: 0.7.2
You are using the latest release

Starting wolframscript by path: /Applications/Wolfram Engine.app/Contents/Resources/Wolfram Player.app/Contents/MacOS/WolframKernel

Wolfram Language 13.3.0 Engine for Mac OS X ARM (64-bit)
Copyright 1988-2023 Wolfram Research, Inc.

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?

[JerryI]

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....whatever../wljs-frontend) and restart

[gganapat]

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: ***@***.***>

[gganapat]

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.

[JerryI]

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...

[gganapat]

ok, I re-activated the free Wolfram Engine (13.3) and pointed to it instead of the MM v14 now it works. Thx!

[JerryI]

Still not fixed
It looks like that most developers still use ugly workaround solutions like this one

[JerryI]

Solutions are listed in docs

[JerryI]

Fixed in signed release
Now we have all certificates from Apple