User Profile

Until recently, I have successfully installed macOS Monterey 12 dev beta updates on my 2013 Mac Pro (the cylinder Mac Pro) with an Apple 27" LED Cinema Display. The Mac Pro is partitioned into two volumes, one of which boots Big Sur. The other volume is intended to boot Monterey, and it did so successfully through Monterey dev beta 7. However, the dev beta 8 and 9 updates cause the screen to go black near the end of the update process, when I need to be able to start clicking on various buttons to finish setting it up. Hitting the Return key just causes the Mac to beep. I have been unable to find any way to see the screen at this point in the process, despite many attempts. Substituting a different monitor yielded the same result. Has anybody else seen this? Can anybody suggest a solution?

I know my Mac Mini DTK boots because I hear it ask if I want to turn on VoiceOver. But my monitor never displays it. The monitor is an LG UltraFine 24" (24MD4KL-B), which the DTK Release Notes specifically say is supported at 4K using DisplayPort alt-mode. But I have connected it both with an Apple USB-C cable and with a Thunderbolt-2 (Mini DisplayPort) cable and USB-C/Thunderbolt 2 adaptor, both of which should support DisplayPort alt-mode, but I get no video -- the monitor remains dark. My old Apple LED Cinema Display 27" doesn't work, either. Any suggestions?

I have a small macOS application with an embedded framework, both written in Swift 3.1. Each has its own Xcode project in separate locations on my Mac, and I use an Xcode workspace to develop and build both at once. I do not use CocoaPods or Carthage. My application and framework build and run successfully in Xcode 9 beta 6 under Swift 3.2.When I try to convert to Swift 4 using the Xcode conversion command, it fails with a "no such module" error for the framework.My online research shows that "no such module" errors have been plaguing developers who use embedded frameworks for several years. A dozen or more solutions have been suggested online, and they apparently work in some contexts but not in others. None of them work for me.Has anybody successfully run the Xcode Swift 4 conversion command with an embedded framework and everything written in Swift? If so, can you spell out the key setup features that made it work for you?

I have a small macOS application with an embedded framework, both written in Swift. Each has its own Xcode project in separate locations on my Mac, and I use an Xcode workspace to develop and build both at once. I do not use CocoaPods or Carthage. My application and framework build and run successfully.When I try to convert to the latest version of Swift using the Xcode conversion command, it fails with a "no such module" error for the framework.My online research shows that "no such module" errors have been plaguing developers who use embedded frameworks for several years. A dozen or more solutions have been suggested online, and they apparently work in some contexts but not in others. None of them work for me.Has anybody successfully run the Xcode Swift conversion command with an embedded framework and everything written in Swift? If so, can you spell out the key setup features that made it work for you?

The NSAccessibility section of the High Sierra AppKit Release Notes say "To see an implementation of using NSAccessibilityCustomAction, please check out the developer sample code project AccessibilityUIExamples." But even the latest version 3.0 of the AccessibilityUIExamples sample code released about a month ago does not implement NSAccessibilityCustomAction. Is this available somewhere else, or will it be included in an update to the sample code?

I successfully installed and ran High Sierra 10.13 dev beta 5 on a Thunderbolt 3 external SSD drive, from which I had booted my Mac when the external drive was a dev beta 4 startup disk. Then I rebooted into the Sierra 10.12 internal drive. All this was on my MacBook Pro (Late 2016) with Touch Bar.Then I discovered this astonishing entry in the dev beta 5 Release Notes: "Volumes with High Sierra beta 5 installed can't be mounted or selected as a Startup Disk on systems running earlier versions of macOS. (33060569)"Sure enough, now I can't find any way to boot from the external drive to continue working on my High Sierra application development.While booted from the 10.12 internal drive, I can use the Startup Disk pane of System Preferences to select the external drive, which is mounted and readable on the desktop and visible in the Startup Disk pane. But when I click the Restart button, I get an error sheet saying "You can't change the startup disk to the selected disk. The bless tool was unable to set the current boot disk."If I choose Restart from the Apple menu and then hold down the Option key, I eventually do see both the internal drive and the external drive, and I can use the arrow keys and the Return key to select the external drive and restart. But, after a lot of flashing lights on the external drive, the Mac restarts into the internal drive, instead.If I shut down and then start back up from the power key while holding down the option key, I eventually see the internal drive and the external drive just like on a restart, but again the Mac eventually boots into the internal drive, instead.If I hold down the C key after restarting to force a boot from the external drive, the Mac simply never boots, even if I let it keep trying for several minutes. Once I let up the C key, the Mac quickly boots into the internal drive.If I hold down the D key after restarting, the Mac goes into diagnostics mode and takes 3 minutes to check everything. It then reports "No issues found."Am I stuck? No more High Sierra development work for the next two weeks, while Apple works on dev beta 6? Or is there some other way I can boot into dev beta 5 on this external drive?