Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Weak Auras Companion 5.2.6 will not display on macOS Sonoma #2601

Open
PedroPolakoff3 opened this issue Sep 6, 2024 · 25 comments
Open

Weak Auras Companion 5.2.6 will not display on macOS Sonoma #2601

PedroPolakoff3 opened this issue Sep 6, 2024 · 25 comments
Labels
bug Something isn't working

Comments

@PedroPolakoff3
Copy link

Install and attempt to startup Companion 5.2.6 on macOS Sonoma and the main window is not visible.
@PedroPolakoff3 PedroPolakoff3 added the bug Something isn't working label Sep 6, 2024
@Stanzilla
Copy link
Contributor

Are you on an Intel or Apple Silicon system?

@lebel
Copy link

lebel commented Sep 8, 2024

Same issue here with the latest version on Apple Silicon.

@Stanzilla
Copy link
Contributor

can you open the developer tools via the menu bar icon and see if there are any errors in there?

@PedroPolakoff3
Copy link
Author

PedroPolakoff3 commented Sep 9, 2024 via email

@mrbuds
Copy link
Contributor

mrbuds commented Sep 9, 2024 •
edited
Loading

Intel system and I’mnot able to get anything, no menu bar either.
…
On Sep 8, 2024, at 18:02, Benjamin Staneck @.***> wrote: can you open the developer tools via the menu bar icon and see if there are any errors in there? — Reply to this email directly, view it on GitHub <#2601 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHOA57QMLCN6HCNI3AVGPXTZVTCQ7AVCNFSM6AAAAABNZM343SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZWHAZTQNBVHA. You are receiving this because you authored the thread.

We release version 5.2.7 that should fix the problem, could you test and report if your problem is fixed?

@DaatDweller666
Copy link

Hi. I have Sequoia MacOS (15.0) on Intel but I think the problem is the same as in Sonoma. When I try to run 5.2.7 from Applications, I get pop up that it cannot be launched. But when I dig into the package and open WeakAuras Companion from Companion.app/Contents/MacOS, Terminal session starts and application runs normally. Of course when I close Terminal, the whole session ends too.

Regards, Lucas

@Stanzilla
Copy link
Contributor

Hi. I have Sequoia MacOS (15.0) on Intel but I think the problem is the same as in Sonoma. When I try to run 5.2.7 from Applications, I get pop up that it cannot be launched. But when I dig into the package and open WeakAuras Companion from Companion.app/Contents/MacOS, Terminal session starts and application runs normally. Of course when I close Terminal, the whole session ends too.

Regards, Lucas

That's a different issue, you have to go to finder and right click open it

@DaatDweller666
Copy link

Hi. I have Sequoia MacOS (15.0) on Intel but I think the problem is the same as in Sonoma. When I try to run 5.2.7 from Applications, I get pop up that it cannot be launched. But when I dig into the package and open WeakAuras Companion from Companion.app/Contents/MacOS, Terminal session starts and application runs normally. Of course when I close Terminal, the whole session ends too.
Regards, Lucas

That's a different issue, you have to go to finder and right click open it

Not exactly. When I go to Finder/Applications and try to open WAC directly from there (RM click + run) I have message that it cannot be opened. However I can open it in the way I described above.

@lebel
Copy link

lebel commented Sep 10, 2024

Intel system and I’mnot able to get anything, no menu bar either.
…
On Sep 8, 2024, at 18:02, Benjamin Staneck @.***> wrote: can you open the developer tools via the menu bar icon and see if there are any errors in there? — Reply to this email directly, view it on GitHub <#2601 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHOA57QMLCN6HCNI3AVGPXTZVTCQ7AVCNFSM6AAAAABNZM343SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZWHAZTQNBVHA. You are receiving this because you authored the thread.

We release version 5.2.7 that should fix the problem, could you test and report if your problem is fixed?

That version didn't fix the issue for me.

@PedroPolakoff3
Copy link
Author

PedroPolakoff3 commented Sep 10, 2024 via email

@PedroPolakoff3
Copy link
Author

PedroPolakoff3 commented Sep 10, 2024 via email

@glanotte
Copy link

Hi. I have Sequoia MacOS (15.0) on Intel but I think the problem is the same as in Sonoma. When I try to run 5.2.7 from Applications, I get pop up that it cannot be launched. But when I dig into the package and open WeakAuras Companion from Companion.app/Contents/MacOS, Terminal session starts and application runs normally. Of course when I close Terminal, the whole session ends too.
Regards, Lucas

That's a different issue, you have to go to finder and right click open it

Not exactly. When I go to Finder/Applications and try to open WAC directly from there (RM click + run) I have message that it cannot be opened. However I can open it in the way I described above.

I updated to Sequoia and am experiencing an idential issue.

Screenshot 2024-09-26 at 18 22 38

If I try launching the package, I get two modals that it cannot be opened. But going into the package contents, right clicking Contents/MacOS/Weakauras Companion and selecting open will launch the terminal window that runs

Last login: Thu Sep 26 18:20:36 on ttys001
/Applications/WeakAuras\ Companion.app/Contents/MacOS/WeakAuras\ Companion; exit
λ /Applications/WeakAuras\ Companion.app/Contents/MacOS/WeakAuras\ Companion; exit                                    ~
18:23:32.918 › App starting...
2024-09-26 18:23:33.670 WeakAuras Companion[38689:3092297] +[IMKClient subclass]: chose IMKClient_Legacy
2024-09-26 18:23:33.670 WeakAuras Companion[38689:3092297] +[IMKInputSession subclass]: chose IMKInputSession_Legacy

which does succeed but is running in the foreground. I am not too familiar with Electron/JS but I can try to see if anything seems off in the package.

@glanotte
Copy link

ok, going to the CLI, if I try opening the application using open I get a different error

λ open WeakAuras\ Companion.app                                                                           /Applications
The application cannot be opened for an unexpected reason, error=Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., NSUnderlyingError=0x60000194c2d0 {Error Domain=NSPOSIXErrorDomain Code=162 "Unknown error: 162" UserInfo={NSLocalizedDescription=Launchd job spawn failed}}}

which led me here - electron-userland/electron-builder#8509

@Stanzilla
Copy link
Contributor

Hm interesting, it does work for me, on several macs actually, which is weird.

@glanotte
Copy link

I didn't break for me until I updated to Sequoia, though I did update xcode build tools at a similar time - so another possibility.

@nazrion
Copy link

nazrion commented Sep 29, 2024

Hi. I have Sequoia MacOS (15.0) on Intel but I think the problem is the same as in Sonoma. When I try to run 5.2.7 from Applications, I get pop up that it cannot be launched. But when I dig into the package and open WeakAuras Companion from Companion.app/Contents/MacOS, Terminal session starts and application runs normally. Of course when I close Terminal, the whole session ends too.
Regards, Lucas

That's a different issue, you have to go to finder and right click open it

Not exactly. When I go to Finder/Applications and try to open WAC directly from there (RM click + run) I have message that it cannot be opened. However I can open it in the way I described above.

I updated to Sequoia and am experiencing an idential issue.

Screenshot 2024-09-26 at 18 22 38

If I try launching the package, I get two modals that it cannot be opened. But going into the package contents, right clicking Contents/MacOS/Weakauras Companion and selecting open will launch the terminal window that runs

Last login: Thu Sep 26 18:20:36 on ttys001
/Applications/WeakAuras\ Companion.app/Contents/MacOS/WeakAuras\ Companion; exit
λ /Applications/WeakAuras\ Companion.app/Contents/MacOS/WeakAuras\ Companion; exit                                    ~
18:23:32.918 › App starting...
2024-09-26 18:23:33.670 WeakAuras Companion[38689:3092297] +[IMKClient subclass]: chose IMKClient_Legacy
2024-09-26 18:23:33.670 WeakAuras Companion[38689:3092297] +[IMKInputSession subclass]: chose IMKInputSession_Legacy

which does succeed but is running in the foreground. I am not too familiar with Electron/JS but I can try to see if anything seems off in the package.

This happens to me as well and have to go into the package contents and run it from there to get it working.

@hgoertz82
Copy link

After I updated the app to version 5.2.7, it no longer opens. I get the message shown in the screenshot.
Screenshot 2024-10-01 at 09 17 02

@nazrion
Copy link

nazrion commented Oct 1, 2024

After I updated the app to version 5.2.7, it no longer opens. I get the message shown in the screenshot. <img alt="Screenshot 2024-10-01 at 09 17 02" width="872" src="https://private-user-images.githubusercontent.com/15179339/372393011-4e30f9b6-0d4b-47b1-85fa-905c080dca6c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mjc3ODk0MDYsIm5iZiI6MTcyNzc4OTEwNiwicGF0aCI6Ii8xNTE3OTMzOS8zNzIzOTMwMTEtNGUzMGY5YjYtMGQ0Yi00N2IxLTg1ZmEtOTA1YzA4MGRjYTZjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDEwMDElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMDAxVDEzMjUwNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWYyMmE3YzM0ZGMwNzA2ZWUyYWE2Nzc0ZGExZWI1YzQzZjM1OTM3NDEyYzAxZDQwOTZmMDdlMTViN2EzOTJkNjAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.F0oCojak6PZXHfXMagovvCVcDP4LBXlKL27KEtUD9wc"See the comments above. If you Show Contents and run it from Contents/MacOS/Weakauras Companion it should work. I have an Intel Mac and it works this way for me since upgrading to sequoia

After I updated the app to version 5.2.7, it no longer opens. I get the message shown in the screenshot. Screenshot 2024-10-01 at 09 17 02

See the comments above. If you Show Contents and run it from Contents/MacOS/Weakauras Companion it should work. I have an Intel Mac and it works this way for me since upgrading to sequoia

@PedroPolakoff3
Copy link
Author

PedroPolakoff3 commented Oct 1, 2024 via email

@Stanzilla
Copy link
Contributor

After I updated the app to version 5.2.7, it no longer opens. I get the message shown in the screenshot. Screenshot 2024-10-01 at 09 17 02

That is something different, you can follow this https://derflounder.wordpress.com/2012/11/20/clearing-the-quarantine-extended-attribute-from-downloaded-applications/

@hgoertz82
Copy link

hgoertz82 commented Oct 1, 2024 •
edited
Loading

After I updated the app to version 5.2.7, it no longer opens. I get the message shown in the screenshot. <img alt="Screenshot 2024-10-01 at 09 17 02" width="872" src="https://private-user-images.githubusercontent.com/15179339/372393011-4e30f9b6-0d4b-47b1-85fa-905c080dca6c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mjc3ODk0MDYsIm5iZiI6MTcyNzc4OTEwNiwicGF0aCI6Ii8xNTE3OTMzOS8zNzIzOTMwMTEtNGUzMGY5YjYtMGQ0Yi00N2IxLTg1ZmEtOTA1YzA4MGRjYTZjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDEwMDElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMDAxVDEzMjUwNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWYyMmE3YzM0ZGMwNzA2ZWUyYWE2Nzc0ZGExZWI1YzQzZjM1OTM3NDEyYzAxZDQwOTZmMDdlMTViN2EzOTJkNjAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.F0oCojak6PZXHfXMagovvCVcDP4LBXlKL27KEtUD9wc"See the comments above. If you Show Contents and run it from Contents/MacOS/Weakauras Companion it should work. I have an Intel Mac and it works this way for me since upgrading to sequoia

After I updated the app to version 5.2.7, it no longer opens. I get the message shown in the screenshot. Screenshot 2024-10-01 at 09 17 02

See the comments above. If you Show Contents and run it from Contents/MacOS/Weakauras Companion it should work. I have an Intel Mac and it works this way for me since upgrading to sequoia

No, unfortunately that doesn't work for me.
I have now managed to open the app. I had to go into the privacy and security settings and click the “Open anyway” button to allow access to the blocked app.

@bloodstrike
Copy link

Also having issue with 5.2.7 on MacOS 15.0 (Intel). For those of you getting the "Apple could not verify..." pop-up, this seems to be the new language for unsigned apps. If you are seeing that, go to Settings -> Privacy & Security and scroll down near the bottom to the Security heading. You should see a message about trying to open WeakAuras Companion and can hit 'Open Anyway' or whatever the message is. You will have to enter your password.

The bad news is that even doing that, I'm sill seeing the "The application "WeakAuras Companion" can't be opened" alert when I try to just open the app normally. However, I was able to get the application to open from a terminal - Open a terminal and type in:

/Applications/WeakAuras\ Companion.app/Contents/MacOS/WeakAuras\ Companion

That seemed to work just fine. Not sure why it won't open normally, but this might help people to be able to use the app until a solution is found.

@Stanzilla
Copy link
Contributor

Ah interesting, looks like Apple has an article about that https://developer.apple.com/news/?id=saqachfa

@nazrion
Copy link

nazrion commented Oct 31, 2024

Also having issue with 5.2.7 on MacOS 15.0 (Intel). For those of you getting the "Apple could not verify..." pop-up, this seems to be the new language for unsigned apps. If you are seeing that, go to Settings -> Privacy & Security and scroll down near the bottom to the Security heading. You should see a message about trying to open WeakAuras Companion and can hit 'Open Anyway' or whatever the message is. You will have to enter your password.

The bad news is that even doing that, I'm sill seeing the "The application "WeakAuras Companion" can't be opened" alert when I try to just open the app normally. However, I was able to get the application to open from a terminal - Open a terminal and type in:

/Applications/WeakAuras\ Companion.app/Contents/MacOS/WeakAuras\ Companion

That seemed to work just fine. Not sure why it won't open normally, but this might help people to be able to use the app until a solution is found.

I am using 5.2.7 and with the latest Sonoma 15.1 patch seems to have fixed the problem because I can open up the app no differently now.

@PedroPolakoff3
Copy link
Author

PedroPolakoff3 commented Nov 3, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@Stanzilla @glanotte @mrbuds @lebel @bloodstrike @hgoertz82 @PedroPolakoff3 @nazrion @DaatDweller666