![]() Does the user really need to know that “Foo Helper” exists and want to really control that separately from the main app? I know for a fact that the vast majority of Hazel users have no idea how the different executables in Hazel work and interact with each other. This is a level of “transparency” that muddles the issue and adds nothing of value. The user should not have to understand the different running components internal to an app. Is this something the user really needs to be exposed to? Minimally, Apple should observe the display name specified by the bundle but in the ultimately, this should not appear there at all. Unfortunately, Apple requires the crazy naming scheme for apps that are login items bundled in the main app. Now, what the hell is that godforsaken app name? Well, it’s the team id followed by the bundle id. You think adding and enabling your app there is all that is needed that it should handle permissions for that app and all its subsidiary executables in its bundle. If you go to that section in System Preferences/Settings, you’ll see a list of apps. One of the main permissions that Hazel may require is Full Disk Access. Nonetheless, it shouldn’t be much of a problem figuring out the responsible app bundle but for some reason, a consistent solution has eluded Apple. There may be multiple executables in the app bundle. ![]() For many apps, though, it’s slightly less straightforward. If the “Foo” executable, which is located in …Foo.app/Contents/MacOS, does something that requires permission, the system knows to present Foo.app as the responsible bundle. Key to this is providing the user with a correct identification of the app in question.įor many apps, this is straightforward. ![]() MacOS Catalina introduced extra privacy protections where the user can control what apps can or cannot do.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |