User Profile

Hi there! I've already posted this through feedback assistant (FB8767409) but posting here also to see if there is anyone experiencing the same issue. It seems that now on big sur, when you try to load a kext, it builds a cache and checks all of kernel extensions available.., the problem is that if there is at least one that can't be loaded, then no one is loaded even when it's fine. Here it's an example. When tried any Big Sur compatible extension with Virtual Box also installed (not compatible so far), the log shown: Error: Error Domain=KMErrorDomain Code=1 "Unable to resolve dependencies: 'org.virtualbox.kext.VBoxUSB' names a dependency on 'org.virtualbox.kext.VBoxDrv', which was not found." UserInfo={NSLocalizedDescription=Unable to resolve dependencies: 'org.virtualbox.kext.VBoxUSB' names a dependency on 'org.virtualbox.kext.VBoxDrv', which was not found.} Even when this has nothing to do when the extension I want to load! :( Reproduced this with several kexts... All other kexts were loaded just fine only after removing VirtualBox kext.., weird :(, this shouldn't be happening and kmutil/kextutil should only check the kext requested by the user to be loaded. Thanks in advance for the feedback!

Hi there! I've searching around, but wasn't able to find any documented way of doing the following.... In summary, it's possible to have a similar api to NSUserDefaults, but to store app common defaults shared by all users? I know I can accomplish that by using custom plist, core data and so on, but I think it'd great to have a similar API like NSUserDefaults but to store common app defaults shared by all users..., Thanks!!

Hi!I've an app that has been notarised without issues until now (last time just some weeks ago). Now is being rejected because it includes an unsigned kext... but the kext is allowed to run and whitelisted at AppleKextExcludeList for years.I guess the notarisation process has been recently changed and is not checking that whitelist, but it should, since it's not taking into account this old kext that run without issues and has been doing so for years.Already opened a FB: FB7642485Is there any other way to continue distributing the app and notarizing under this new policy? Do I need to sign the app with the developer certificate instead of Dev ID? Any ideas?Thanks!

Hi!Well, It seems there is a bug on macOS Catalina when using several monitors in vertical disposition, main one below. If you click on the status bar over a NSStatusItem under this configuration, and the app uses popUpStatusItemMenu to pop the menu, then it doesn't work when clicked on the main monitor. No error log either.., just nothing appears.I know it's a strange behaviour, but could reproduce it with several apps, including testing ones. I also know this method has been deprecated on 10.14, but that doesn't mean it shouldn't work and in fact, with Mojave, the method works perfectly fine under same circumstances.When using other alignments (left to right and so on) this doesn't happen.Opened a case: FB7456388Thanks for reading! Hope this gets fixed on current Catalina beta.

.. I'm afraid that's true 😟, when I say all, I mean ALL of them.At first opened another thread thinking the issue was present only for a bunch of kexts, but after days of randomly picking kexts and trying (some of them very popular), none worked and always displayed same error.Including here a couple of additional examples (tried more, like kext to disable turbo boost, a wireless external card driver, hp printer driver, etc).- osxfusefs (com.github.osxfuse.filesystems.osxfusefs)- ACPIBackling (com.darwin.driver.ACPIBacklight)Always same error. After aproving on system preferences and rebooting, running sudo kextutil -v /path/to/kext displays "...allowing to load" to inmediately show "... unable to calculate CDHash, disallowing load".In the meantime, vmware keeps failing, also virtual box (both have unsigned extensions on that list), etc.Here is the output of the couple of examples..., already reported through feedback assistant....kext file:///Library/StagedExtensions/osxfusefs.kext/ is in hash exception list, allowing to load Skipping migration.plist import (allowBundleIDs:41, cdhashArrayRef:41) { URL = "file:///Library/StagedExtensions/osxfusefs.kext/", ID = "com.github.osxfuse.filesystems.osxfusefs" } is missing or has an invalid CDHash. Disallowing load. Kext rejected due to system policy: { URL = "file:///Library/StagedExtensions/osxfusefs.kext/", ID = "com.github.osxfuse.filesystems.osxfusefs" }And the other onekext file:///Library/StagedExtensions/ACPIBacklight.kext/ is in hash exception list, allowing to load Skipping migration.plist import (allowBundleIDs:41, cdhashArrayRef:41) { URL = "file:///Library/StagedExtensions/ACPIBacklight.kext/", ID = "com.darwin.driver.ACPIBacklight" } is missing or has an invalid CDash. Disallowing load.Reported as FB6516891 and FB6498867 including kexts to try.There are more than 9.000 kexts on that list..., can't believe on beta 3 this hasn't been fixed yet.., embarrasing. No need to say all of those extensions load without issues on Mojave and previous versions.Guys! Let's keep reporting it so the hear us! 😟, no feedback yet

Hi!After trying some apps with the new beta... found some didn't work..., and just discovered it was to this first beta of macOS 10.15 not including AppleKextExcludeList :O :OThere are thousands (literally) of trusted entries specifically.., is this intended or maybe is just a bug and future versions of versions will include it like on all previous macOS releases? a LOT of software relies on this in order to run properly, including some famous apps like vmware, etc.Thanks in advance and best regards.