xattr -p com.apple.quarantine:
This command reads and prints the value of the “com.apple.quarantine” extended attribute for a specified file or directory. The “com.apple.quarantine” attribute is often set by macOS to indicate that a file was downloaded from the internet and may need user confirmation before it can be opened.
xattr -d -r com.apple.quarantine:
This command deletes the “com.apple.quarantine” extended attribute from a specified file or directory, and it does so recursively (-r) if the target is a directory. Removing this attribute effectively clears the quarantine status, allowing the file to be opened without any warnings from macOS.
Great! Thanks for the info! I can also confirm that executing the commands allows KMyMoney 5.1-3138 to work rather well on a MacBook with an M1 chip running macOS Sonoma 14.5. However, for me the home page doesn’t load, and none of the table reports display either. I thus hypothesize there is a problem specifically with rendering tables (diagrams display correctly).
Overall, an easier solution and more convenient compared to using VMware Fusion with the Ubuntu ARM version, which is what I have been using until now.
The display problems on the homepage and the tabular reports appear to be due to the lack of support for the QWebKit/QWebEngine used to display HTML pages on MacOS. In the current master version, displaying HTML content has been implemented using QTextEdit, which solves the problem.
That would be perfect but I think mac os x builds are still stucked and not completing since march.
Which skill are needed to try to provide any help with build issues? Not sure I can help but…
2024-07-14 20:26:29,829 DEBUG sftpnotary.util stderr:
b'/Users/gitlab/ws/builds/GZwHuM5x/0/office/kmymoney/macos-64-clang/build/extragear/kmymoney/archive/Applications/KDE/kmymoney.app: a sealed resource is missing or invalid\n'
Error: Running codesign failed
Command ['/usr/bin/arch', '-arm64', '/usr/local/bin/python3', 'ci-notary-service/signmacapp.py', '-v', '--config', 'ci-utilities/signing/signmacapp.ini', '/Users/gitlab/ws/builds/GZwHuM5x/0/office/kmymoney/macos-64-clang/build/extragear/kmymoney/archive/Applications/KDE/kmymoney.app'] failed with exit code 1
This points into direction of code signing, so building the application in general was successful. Maybe getting in touch with someone who is more knowledgeable about the process and what might cause it would already help. Another idea is to check if another project on invent.kde.org ran into the same problem and how they resolved it.
KMyMoney has been recommended by a friend. Unfortunately I have only access to an old Macbook x86 running MacOs 11.7.10. Any hope that the x86 MacOS Version will be available again?
It’s a shame that I can’t help out here. I hope to meet up with someone who can support us (person is yet to be identified) at akademy and spend some time to fix the problem. If you read this and can help: please let me know.
Is there an update regarding macOS build issue? Currently, stable and development macOS build all have the “bundle resources modified” status - files inside the app bundle were modified since the app was signed - which upsets macOS gatekeeper to block the app with “kmymoney.app is damaged” message, although there are ways to circumvent this and app will run perfectly.
It appears to be an issue regarding macOS build signing and notarization, which is reflected by the error message ipwizard posted earlier. I have tried to find a cause but it is hard to start with build log truncated and unable trace from the final error.
I tried to build myself with no success. With homebrew, KDE Homebrew formulae uses ki18n formula from official Homebrew repository but it’s been since updated from KF5 to KF6 causing kf5-kconfigwidgets build fails due to missing kf5i18n dependency (Homebrew Formulas for KDE Issues #62).
Building with KDE Craft also gives error as it keeps trying to pull stable Alkimia 8.1.2 and kmymoney master requires newer 8.1.80.
I’m not able to resolve or circumvent any of the above issues, hopefully someone with more knowledge could fix these so we can start having macOS builds.
I was wondering if there is any update here. I’m using the Apple silicon and not an intel mac. However, the arm64 download is giving me this error, despite the download page’s suggestion that it works.
