In the previous versions, NCWidgetProviding protocol and the widgetPerformUpdate methods was available from iOS 8 upwards. Now, it's available only from iOS 10 and up (and deprecated due to the new style widgets). That means we can not made to support anymore pre iOS 10 devices with widgets? Old version: https://web.archive.org/web/20190616052107/https://developer.apple.com/documentation/notificationcenter/ncwidgetproviding https://web.archive.org/web/20190619075121/https://developer.apple.com/documentation/notificationcenter/ncwidgetproviding/1490262-widgetperformupdate Current version: https://developer.apple.com/documentation/notificationcenter/ncwidgetproviding https://developer.apple.com/documentation/notificationcenter/ncwidgetproviding/1490262-widgetperformupdate

Hi, Anyone found a way, to prevent automounting the downloadable components (watchOS 9 SDK/simulator and tvOS 16 SDK/simulator) from Xcode 14 on every boot? Maybe, changing the 'mountPolicy' property on '/Library/Developer/CoreSimulator/Images/images.plist' will works? If it works, or if I are already umounted the dmg's, there are any way to manually mount it? Because, i need to reboot my Mac, if i would like to do something in Xcode that are related to watchOS/tvOS.

I have a small application (already published to the Mac App Store) to monitor, and notify the user of some important state changes about thier computer. To display Wi-Fi informations, I listening on the "State:/Network/Interface/.*/AirPort" events of the System Configuration framework. Before 14.4, the returned dictionary had an "SSID_STR" property which was contained the connected network name, but from 14.4, if "SSID_STR" are presents, it's will be always an empty string (""). My first idea was to put "NSLocationUsageDescription" into the Info.plist (and enable Location under App Sandbox in the Signing & Capabilities section) and try to request permission with the Core Locations requestWhenInUseAuthorization call, but even if i had the correct permission (.authorizedAlways), this will did not came to success. There are any workaround or entitlement available to get back the access to this information?