-
-
Notifications
You must be signed in to change notification settings - Fork 357
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
os.setTray crashing app on macOS Catalina 10.15.7 #615
Comments
Also affecting macOS 12.1, FWIW. |
Not trying to be too impatient but is there any update on this as to what is the underlying issue? |
Not sure if it will help but the os.setTray works for me on M1 Mac running Monterey 12.1 (Safari 15) (Rosetta2 installed). Is there something in the setTray code causing the crash or is it a Catalina thing? eg: Neutralino.init();
|
It does not for me, but I'm on an Intel, not a M1 MB. This is the relevant call stack:
|
Looks like an Intel only issue then although Rosetta2 should react the same .... |
Was kind of curious as to where the above call stack was coming from and I get it whenever I open the Inspect Element dev console after the app has launched (double-clicking executable) - this occurs even if the previous code (setTray or extn code) has worked successfully or not. I will get these logs in this scenario on 12.2 Monterey back to 10.13 High Sierra. If the executable is packaged as a normal mac app (exec is in MacOS folder/ app files in Resources folder) and launched normally there is no problem. |
Yeah sorry about that I think the above call stack is indeed unrelated to the actual issue with setTray
Now you're referring to setTray or the warning from above? |
Yea - the warning above only occurs when the dev tools are opened (WKInspectorWKWebView) when using the executable directly in terminal mode. |
This still seems to be a problem with the First Neutralinojs App (macOS 10.15.7, Intel MacBook Pro). I get I just tested with Neutralino Server 4.4.0, Client 3.3.0 (build from a couple days ago). Using the documented procedure for creating the First Neutralino App,
BUT... Changing the starter app code to call setTray() (comment out the
What other information could I collect? Thanks |
Update:
|
@shalithasuranga Why would a macOS build try to include bin/neutralino-linux_ia32? (see above) Thanks. |
Just for curiosity does anyone have an example of code within the setTray() function that fails or does it only fail when using the CLI? eg: I do know that if say the icon path option is unavailable or misspelt then the app will crash with a segmentation trap. |
Segmentation fault means it's a problem inside the Neutralino C++ Code itself and not the client file |
Yes that may be the case. As far as I can see for me the setTray works OK in a normal mac app scenario provided the icon path etc is OK but it appears that the issue may be occurring if the CLI is being used. I have noticed that even with the CLI if the icon path is not right then a crash will occur. Update: just tried the latest CLI (9.2.0 with server 4.4.0 and client 3.3.0) on 10.13 and 12.2 M1 and setTray() works well for me - I was using npx to create/build/run as I don't like global installs so maybe there is an issue only with the global install on M1's. |
If it helps, this currently works on Monterey 12.3 |
Any workarounds for this or ETA for when this will be fixed? 😢 |
If the issue is a segfault, then you could perhaps try if #1010 fixes the issue. It adapts to changes to the |
Any updated on this? Been open for a while by the looks of it |
It's still not working on Ventura 13.2 and neutralinojs 4.11.0, any clues to fix that? |
On a M1 MPB with Monterey v 12.6 - I commented-out the conditional check Edit: Since the starter app code links to this issue in a comment, It might be helpful for the conditional check to more specifically look for the affected macOS version. The demo example, as is, gives the impression—to folks going through the "Your First Neutralinojs App" journey—that |
This issue also exists on Ubuntu 22.04. I'm using
|
any news? |
Re-asking if any workaround was found? |
Ref: #614
The text was updated successfully, but these errors were encountered: