Search Results

I am trying to figure out how to retain root access after reboot (like Parallels does) for certain functions. So for example, fan control... this requires root access. If I wanted to create a fan control software that ran in the toolbar, but needs to retain root access after reboot (to keep the same control/fan profile, etc), is this accomplished by asking to add permissions in system prefs, or is this accomplished some other way?

Hi, In implementing MDQuery which tracks file changes - I have noticed that when receiving the "kMDQueryUpdateRemovedItems" notification - the item path is null. In order to track the file creation/update/removal life cycle - I need some common "thread". It seems like internally MDItem has a unique identifier field called "oid" - however it is not exposed through public API. It seems like relying on the pointer is a bit of a "medieval" solution, so the question is - how do I get access to the "oid" please? Thanks.

Hey guys! Was wondering if you guys knew where the macOS icons in BigSur are stored. I checked in the following places and pretty much the whole /System/Library folder: /System/Library/CoreServices/CoreTypes.bundle/Contents/Resources -- where they usually are Finder app in /System/Library/CoreServices/Finder.app Dock app in that same directory CoreTypes.bundle in /System/Volumes/<whatever your startup disk is named>/System/Library/CoreServices/CoreTypes.bundle/Contents/ I need those icons for stuff. Please let me know if you guys know where they are!

What is the process named "announced" on iPhone 6S, iOS 14.4? Is it safe? Found zero information about it.

What is the process named com.apple.dt.DTConditionInducerSupportService on my iPhone 6S, iOS 14.4?

I wish to improve/update the functionalities and services offered by an iOS framework for my application. What are the ways by which I can do the same ?

Over the past couple of weeks we've seen an increase in crashes on launch reported by users. On retrieval of these crashes from their devices (as they were not reported in Xcode) it became apparent that they were watchdog 0x8badf00d terminations. Having consulted the documentation on Addressing Watchdog Terminations - https://developer.apple.com/documentation/xcode/diagnosing_issues_using_crash_reports_and_device_logs/identifying_the_cause_of_common_crashes/addressing_watchdog_terminations the crash reports suggest the app is mostly idle as the elapsed application CPU time is very small (0.134s) compared to the total elapsed CPU time (28.57s). What seems concerning is that the reports show almost all threads are locked (__ulock_wait) in libobjc waiting on either class look-up (look_up_class) or method dispatch (_objc_msgSend_uncached/lookUpImpOrForward), bar two queues, one of which is waiting on another queue and the other of which is inspecting images loaded by dyld (likely hitting the same lock?). There's nothing immediately apparent suggesting our app is doing anything to trigger this (the main thread is simply waiting on an object to be initialised). All crash reports present the exact same series of frames on the main thread which suggests it's not something happening beforehand taking a large amount of time (which I'd expect to be more variable). For all users re-opening the app again it works fine. Here's one of the clearest crash reports - https://gist.github.com/SquaredTiki/11a58e6837029e44da6098b34486658d (we've seen it occurring on iOS 14.2 and above). Any ideas what might be happening here?

Hi everyone, since in iOS 14 it is possibile to change the default app for emails, and also the browser, how can I retrive which is the default app? more precisely I need to know if the default app is "Mail" (of Apple) or something else. Thanks in advance

In Big Sur, I noticed that the open command no longer distinguishes different copies of an application. For example, if I have /Applications/AppV1.app and /AppicationsAppV2.app, and AppV1.app is running, then open /Applications/AppV2.app is simply bring AppV1.app rather than opening AppV2.ap. I have to use the -n flag to open the second version. This seemed like a regression to me (I filed FB8806330 about it), but perhaps intentional, or at least justifiable. But now I've discovered a much worse symptom. If App.app and Bpp.app is another application by my company, then open /Applications/Bpp.app brings App.app to the foreground rather than opening Bpp.app. All the applications have distinct bundle identifiers. Indeed open -b com.Company.Bpp will also bring App.app to the foreground. This is just a crazy bug, right? Any ideas what it might be keying off? It can certainly tell the difference between our apps and, say, Safari. So I'm not sure why it can't tell our applications apart. And if anyone from Apple is here, should I add this worse symptom to my existing FB, or open a new one? Thanks

what is the best way for a HAL plugin to launch a helper app? i tried the obvious NSWorkspace's launch/openApplication those don't work. HAL plugin works in the context of coreaudiod which makes that tricky.

We've noticed that our app is now immediately crashing on background on iOS 14 Beta 3 with the 0xdead10cc termination reason. This indicates (as per Technical Note TN2151 - https://developer.apple.com/library/archive/technotes/tn2151/_index.html) that the app held on to a file lock or sqlite database lock during suspension. However this crash didn't occur at all prior to beta 3. Did something change in iOS that might cause this? Stricter enforcement? This is a hard crash for us to debug with little than the technical note to go on and potentially an unknown change in iOS itself.

Our application is hanging on launch. Looking at the callstack we have a call to CFBundleGetFunctionPointerForName which eventually causes another call to CFBundleGetFunctionPointerForName. We hang with the following subset of the callstack: 2550 CFBundleGetFunctionPointerForName	(in CoreFoundation) + 39	[0x7fff2c0bdd4a] 		+																																																																																									 2550 _CFBundleLoadExecutableAndReturnError	(in CoreFoundation) + 316	[0x7fff2c0f5e0f] 		+																																																																																										 2550 _pthread_mutex_firstfit_lock_slow	(in libsystem_pthread.dylib) + 211	[0x7fff6dc89218] 		+																																																																																											 2550 _pthread_mutex_firstfit_lock_wait	(in libsystem_pthread.dylib) + 81	[0x7fff6dc8b31d] 		+																																																																																												 2550 __psynch_mutexwait	(in libsystem_kernel.dylib) + 10	[0x7fff6dbc21be] Do we need to refactor our code to prevent recursive calls or is this a bug in 10.16?

Hi everyone, I guess the question gets bizarre. Is it possible in Swift to read the signals picked up by the antennas of my device? I just mean the raw signals not like Bluetooth service, Wifi service, etc. Just everything that is picked up by the antennas, whether it is a signal relating to the service for which the antenna is designed or not. Thanks for any suggestions. Alex

I have a launch daemon (via launchd) that requires access to the macOS built-in camera to do some video processing using OpenCV. Since macOS Catalina (I believe in Mojave also), my launch daemon has no access to the camera at all. No security prompts - nothing at all. I tried the same trick as I did for "Input Monitoring": Pack the daemon in an app-like structure, whitelist the camera in harden runtime, and run the daemon's code as an application. In that case, I do have a security prompt as expected and my code works with the camera. Also, I get my application listed under "Privacy" - "Camera". Unfortunately, whenever I try to launch the same binary as a daemon using launchd, I get no access to the camera. No matter whether my daemon-application was added before under "Privacy" - "Camera" or not. The approach above worked with "Input Monitoring" but not with the camera (for "Input Monitoring" I launched the daemon as an app to whitelist it first and launched it later via launchd). Is that a bug? Or launch daemons are not allowed to access the camera in macOS Catalina in any case? Any ideas?