-
-
Notifications
You must be signed in to change notification settings - Fork 133
[BUG]: v4.8.2 does not run on macOS/silicon #1679
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
Comments
I should add that I'm using I'm using Apple silicon (the M2 chip) |
Hi, yes, that is entirely possible because all RSS Guard macOS binaries are "blind compiled" - in other words, I do not have either Mac OS X machine or other way to actually develop/test/debug RSS Guard on Mac OS X operating system. So, yes, eventually it just happens that RSS Guard hits some bug. As said above, I am not really able to effectively solve the bug you have. You could try to build RSS Guard from sources. |
Thanks Martin. I'll see if I can work out how to do that. Meanwhile I've tested it on an intel Mac (also running macOS 15.4) and it runs fine, so the problem is specific to Apple silicon. I can confirm that there was no such problem with previous versions. |
Apple Silicon is to my knowledge ARM-based architecture, not x86(_64). Therefore RSS Guard cannot physically run on Apple Silicon. I could be wrong, tho. Any maintainers with atleast basic C++ skill and Mac OS X machines are welcomed to carry about Mac OS X compatibility. |
RSS Guard has run fine on Apple silicon until version 4.8.2 |
Apple Silicon is to my knowledge ARM-based architecture, not x86(_64). Therefore RSS Guard cannot physically run on Apple Silicon. I could be wrong, tho. Any maintainers with atleast basic C++ skill and Mac OS X machines are welcomed to carry about Mac OS X compatibility. |
I have spent some time debugging this. Here is the first part of the macOS diagnostics report, which reveals the problem:- --begin quote--Translated Report (Full Report Below)Process: rssguard OS Version: macOS 15.4 (24E248) System Integrity Protection: enabled Crashed Thread: 0 Exception Type: EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid)) Note that the application runs natively on ARM-64. The problem seems to be an error in code signing. Explaining why the app runs on an Intel Mac but not (in the case of v4.8.2) on an Apple silicon Mac is the fact that apparently Intel-based devices can still run unsigned code whereas for Apple silicon devices, all code must be signed. I found a workaround, though. Having run
the app is forcibly signed (or resigned, as the case may be) locally with an ad hoc signature, following which it may be opened successfully. Ideally, the code signing issue would be resolved, but I'm not sure I can be of much help in identifying the precise problem. With many thanks for such a great app. |
@lollyP Do you run "codesign" command on the app folder or directly on the app DMG file? |
I added signing directly to the compilation script, now the binaries should be signed. Can you please test with latest development build once it compiles? https://github.com/martinrotter/rssguard/releases/tag/devbuild |
@martinrotter codesign is run on the installed app folder, so the command is better expressed as
Thank you - I will test the development build as soon as I am able, which is likely tomorrow. [For the benefit of others, in case this issue arises again or crops up in connection with other apps, '--deep' ensures that all files within the app directory are signed, '-f' ensures that pre-existing signatures are replaced and '-' prescribes an ad hoc signature.] |
I have tested v4.8.3 and unfortunately the issue remains. As with v4.8.2, the system diagnostics report reports the same error and the codesign command provides a workaround. |
I added codesign command to build script. Could it perhaps be that it must be signed on silicon machine to run on silicon machine? https://github.com/martinrotter/rssguard/blob/master/resources/scripts/github-actions/build-linux-mac.sh#L147 |
That's possible but I'd be out of my depth commenting further. Could you perhaps leave this issue marked 'open' and wait for someone more knowledgeable than me to comment? I fear this one has already taken up a disproportionate amount of your time. |
Running codesign with sudo on the Application seems to work for me. |
Reproducible:
|
4.8.3 doesn't run at all, says that the application is damaged |
That is not completely true, if I have understood it well. MacTerrassa P.S. Mechanically translated message since I do not speak English, I apologize if I have not expressed myself correctly. |
Brief description of the issue
Having got past gatekeeper, version 4.8.2 simply does not open on macOS 15.4.
I've tried all the obvious things including a clean install. I am unable to generate a bug report as when I attempt to run the app from a terminal window, I get just "Killed: 9".
How to reproduce the bug?
What was the expected result?
app should open
What actually happened?
app did not open
Debug log
n/a - see above
Operating system and version
The text was updated successfully, but these errors were encountered: