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.

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

Opening app the usual way fails #3

Open
pfahlstrom opened this issue Nov 22, 2024 · 5 comments
Open

Opening app the usual way fails #3

pfahlstrom opened this issue Nov 22, 2024 · 5 comments

Comments

@pfahlstrom
Copy link

Hi there! I just downloaded your fork today, and I'm having trouble running the app. I stuck it in the Applications folder and double-clicked it, and I got the message saying Apple can't verify the app and I should delete it. So I right-clicked it and selected Open, and still got the same message. After that, I used the xattr command to remove the app from quarantine, and then when I double-clicked it or right-clicked it to Open, nothing happened. I try to open it and...nothing. It shows the standard animation of an opening app icon, but the app does not actually open.

I used Show Package Contents on the app and navigated to the Contents/MacOS/ folder, and double-clicked on Hermes there. Apple then showed the same pop-up warning that Apple can't verify the app. So I ran the xattr command on that executable too.

After I did that, the app DOES run if I double-click the executable in Contents/MacOS/ — but only with its respective Terminal window open. (However, strangely enough, the application windows don't have any shadows around them. Very odd.) Double-clicking the .app file still doesn't work.

@inieves
Copy link

inieves commented Nov 22, 2024 via email

@dtseto
Copy link
Owner

dtseto commented Nov 22, 2024

Appreciate this. On newer mac os the running of unverified apps is made harder. I have a developer account but it is not completely set up yet. When I get my apple silicon mac setup I hope to get the developer account set up completely so I can sign the apps and debug the UI bugs that are in the apple silicon version but not on the intel version. Again thank you for testing and commenting feedback is valuable for devs.

From apple

"To open an unsigned app on macOS 15 (also known as "Sequoia"), you need to manually override your security settings by going to System Settings > Privacy & Security > Security, then click "Open Anyway" when attempting to open the app, confirming that you want to open it despite it not being signed by a trusted developer; however, be aware that doing so can potentially expose your system to security risks. "

Hi there! I just downloaded your fork today, and I'm having trouble running the app. I stuck it in the Applications folder and double-clicked it, and I got the message saying Apple can't verify the app and I should delete it. So I right-clicked it and selected Open, and still got the same message. After that, I used the xattr command to remove the app from quarantine, and then when I double-clicked it or right-clicked it to Open, nothing happened. I try to open it and...nothing. It shows the standard animation of an opening app icon, but the app does not actually open.

I used Show Package Contents on the app and navigated to the Contents/MacOS/ folder, and double-clicked on Hermes there. Apple then showed the same pop-up warning that Apple can't verify the app. So I ran the xattr command on that executable too.

After I did that, the app DOES run if I double-click the executable in Contents/MacOS/ — but only with its respective Terminal window open. (However, strangely enough, the application windows don't have any shadows around them. Very odd.) Double-clicking the .app file still doesn't work.

@pfahlstrom
Copy link
Author

Using the xattr command used to work too. Anyway, I just deleted the app, downloaded it again, and put it into my Applications folder. When I got the error, I followed the above steps in System Settings to allow me to open the app. Now I can double-click on it, but the app still does not open. It still fails silently as I wrote above.

@pfahlstrom
Copy link
Author

Responding here to your comment on the other bug since it's about this issue.

I tried beta 4, beta 3, and your first 1.3.2 app version. After downloading and installing and using System Preferences to bypass the security check on all 3 of them, they all exhibit the silent failure upon app launch. I have no idea why.

@dtseto
Copy link
Owner

dtseto commented Nov 26, 2024

This is probably caused by stricter apple silicon requirements for code signing etc. It will require a refactor that breaks compatibility compatibility with older mac os so macos 11+ only. Current version inherited from original hermes is mac os 10.10+.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants