trilemma-dev / blessed Goto Github PK

Hey Guys!

We are using your package in our app AlDente since a few months ago and we are generally very happy with it. Blessed really makes the workflow of installing the helper application much easier. Thank you for your great work!

This being said, we have received some feedback from our users that AlDente apparently is marked as a trojan bitcoin miner by one antivirus software called "DrWeb". See this issue.
After searching around what could have introduced this flag, I found that if I remove Blessed from the project, the antivirus doesn't detect it as a trojan anymore.
I am not in any way suggesting that this library has any malicious intent. Like I already wrote in the statement on the issue, I am very sure that this is a false positive by DrWeb.

Do you have any idea on why Blessed could be the reason for this false classification? If you need any extra info like the test-compiled version without Blessed or some implementation code, please let me know.

Thank you for your help and kind regards,

David
AppHouseKitchen

let icon = Bundle.main.url(forResource: "bless", withExtension: "png")

When I use the above code, and add an image called "bless" to my App, I am not get the actual image icon, instead I get a file icon with the letters "PNG" on it.

Are there any specs for the image such as image size, or any thing else that might be missing?

Hello!

I'm attempting to use this as a part of an application running a privileged helper, and am using SwiftAuthorizationSample as a jumping off point. I've been having issues getting this to function in my own app, so here is a short summary:

I started off by running the SwiftAuthorizationSample project, just changing the Signing ID to my developer ID. When running the project, it worked flawlessly, installed the helper tool, and I could see it located in /Library/PrivilegedHelperTools. Success!

So, I started initially by going through the code in that project to create my own version which accomplishes running a privileged command in a different communication method. This is when I first ran into the problem of it not installing. It threw a Blessed.LaunchdError error 3. This would come to haunt me.

My initial thought was that something in my implementation had been wrong. So, out of curiousity, I began by recreating the helper tool, and the shared resources in my project, knowing that if I can get those to work, it's my implementation, and not my project files. I dragged and dropped, verified that my Info.plists were correct, run scripts, even scrolling through Build Settings side by side to make sure they matched.

No such luck. Ouch.

So then I tried to back trace where this error could be from. When I followed where it was running, I figured that it had to be an error thrown at line 81 in LaunchdManager.swift in the Blessed package. I couldn't find anywhere explicitly throwing an authorizationError, soooooo.

I then figured I'd take a look at the errors in both this project, as well as SwiftAuthorizationSample, and the closest issues I could find are #8 and #6 both of which seem like they should have been resolved by this solution. The root of the problem seemed to be addressed, which was that the Signing ID's needed to be in quotes. As my code pull was after this change, I'm not sure what could be the issue.

When I ran the install code, it showed a dialogue, I entered my password, and without a doubt, every time, it would throw that error. I double verified everything again. After all, it has to be me. The only issue that it could be is that the app may not have permissions to write to /Library, but the .xcconfig states that it should not be sandboxed, and I was unable to get the NSApplication.isSandboxed() check to return anything, as it always just threw an error when running.

I've done my best to ensure that all of the settings are true to what they should be, the project is indeed using the correct .xcconfig files, and all information is true. It does in fact copy the helper tool to DerivedData/Build/Products/Debug/Maple/Contents/Library/LaunchServices/dev.halz.Maple.helper. This is the output of DiagnosticSigningInfo.printDiagnosticInfo():

==============This App=============
2022-05-10 09:41:30.260574-0400 Maple[5475:141871] [logging-persist] cannot open file at line 45530 of [9ff244ce07]
2022-05-10 09:41:30.260631-0400 Maple[5475:141871] [logging-persist] os_unix.c:45530: (0) open(/var/db/DetachedSignatures) - Undefined error: 0
CFBundleIdentifier: dev.halz.Maple
CFBundleVersion: 1
Common Name: Apple Development: My Name (CT44P6LGD8)
Organizational Unit: 5RD23JCCKU

========Bundled Helper Tool========
CFBundleIdentifier: dev.halz.Maple.helper
CFBundleVersion: 1.0.1
Common Name: Apple Development: My Name (CT44P6LGD8)
Organizational Unit: 5RD23JCCKU

=======Installed Helper Tool=======
Helper tool is not installed

I appreciate any input you have in this issue! It's much appreciated.

There are major changes with the introduction of SMAppService .

First off, sorry if this is user error rather than specifically a Blessed/SecureXPC question:

I'm attempting to debug my app in Catalina as my helper is crashing both there and in Big Sur (it runs fine in Monterey). To this end I've installed macOS Catalina 10.15.4 on a partition and set up Xcode 12.4, which is the latest available for 10.15. I've also installed and selected the Swift 5.6.1 toolchain.

Despite selecting the 5.6.1 toolchain, I get "Failed to resolve dependencies": "because every version of Blessed contains incompatible tools version and root depends on Blessed 0.3.0..<1.0.0, version solving failed."

Am I missing something? Has anyone else successfully used Blessed/SecureXPC in Xcode running on Catalina?