I just installed both Xcode 16 Beta 6 and Xcode 16.1 Beta. I made a quick macOS test app. In both Xcode 16 Beta and Xcode 16.1 Beta, the Minimum Deployment is limited to macOS 11 Big Sur (specifically macOS 11.5). In Xcodes 15, 14, and 13, the Minimum Deployment could be set down to macOS 10.13. I glanced at Xcode 16's Release Notes and didn't see any mention of 11 Big Sur being the new Minimum Deploy Target for macOS apps. Moving forward, will Xcode 16 be limited to supporting just 5 versions of macOS (Sequoia, Sonoma, Ventura, Monterey, and Big Sur)? Or is this just something for the Beta (a bug perhaps)? Hopefully the Minimum Deployment Target for macOS apps be lowered back down to 10.13. Thanks.

Hi - I’m trying to move over my current project from Xcode 14 to Xcode 15 and having some issues with the new Mergeable Libraries feature. Specifically, Xcode 15.0.1 appears to be taking several of my old Xcode 13 and 14 pre-built Frameworks and merging their binaries into the main executable. But it’s doing this despite all the “Merge” Build Settings being set to NO in my main project. Furthermore, Xcode 15 is only doing this to my older pre-built Frameworks. My project also creates several other Frameworks at build time, but Xcode 15 doesn’t seem to be merging those Frameworks into the main executable. So I’m confused. Since I'm new to Xcode 15 and Mergeable Libraries, I was wondering: Is this expected behavior in Xcode 15 or should I file a bug? I would think that the Mergeable Libraries system would be opt-in, and I haven’t done anything to activate it. Thanks.

I was reading through this post: https://developer.apple.com/forums/thread/718583 I've been able to reproduce this behavior by double-clicking a DMG in the Finder while the Mac is Offline. I checked the Notarization status of the app via spctl and it shows "Notarized Developer ID". So sure enough, Quinn's comment about Gatekeeper "ingesting" the notarization ticket stapled to the DMG and automatically applying it to the app inside is 100% spot-on. However, I can't seem to get the same behavior to happen when mounting the DMG via hdiutil in Terminal. While Offline, I do a: hdiutil attach /path/to/my/dmg.dmg and then spctl -a -t exec -vvv /Volumes/path/to/my/mounted/dmg/myapp.app After the spctl I'm seeing /Volumes/path/to/my/mounted/dmg/myapp.app: rejected source=Unnotarized Developer ID origin=Developer ID Application: My Developer Creds (XXXXXXXXXX) Is there a way to get Gatekeeper to "ingest" the notarization ticket stapled to the DMG when using hdiutil while Offline? Note 1: If I use hdiutil while online, everything works as expected. Note 2: I'm testing all this via a VM of macOS 12.7.1, if that makes any difference. Thanks!

Sandbox testing had been working great for me up until about 22 hours ago. Since then, all my Mac App Store apps have been getting: Error fetching receipt - Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={kCFStreamErrorDomainKey=4, ), NSLocalizedDescription=The request timed out., NSErrorFailingURLStringKey=https://p100-sandbox.itunes.apple.com/WebObjects/MZFinance.woa/wa/createAppReceipt, NSErrorFailingURLKey=https://p100-sandbox.itunes.apple.com/WebObjects/MZFinance.woa/wa/createAppReceipt, _kCFStreamErrorCodeKey=-2102} Apple's System Status pages have consistently reported "green" across the board during this time. This has been happening with all of our Mac App Store apps. I've tried testing using: Various different Macs, various OS X User accounts, various Sandbox accounts, and various versions of OS X. I went so far as to try an offsite Mac across town that's on a different IP & DNS. No bueno. Any suggestions (other than to file a report with Apple)? Thanks!

For the past week I’ve been unable to prepare new Mac applications for submission to App Store Connect. macOS isn't providing my apps with MAS Receipt data at launch time when testing with App Store Connect Sandbox users. I discovered this when I started working on an update for one of our apps. But I’ve found that almost all of our other published apps are exhibiting the same behavior. When our apps are launched, we check for the existence of MAS Receipt data in the app's package (ie, MyAppName.app/Contents/_MASReceipt/receipt). When the receipt doesn’t exist our apps call exit(173) as per Apple’s guidelines. At that point, macOS typically downloads the MAS Receipt data and re-launches the app for us. However, after the call to exit(173) no Receipt data is downloaded, and the Finder reports the app as being “Damaged”. An inspection of the Console log reveals the following: loginwindow -[PersistentAppsSupport applicationQuit:] | for app:MyAppName, _appTrackingState = 2 loginwindow -[PersistentAppsSupport applicationQuit:] | App: MyAppName, quit, updating active tracking timer storeuid ReceiptRefreshRequest: Error fetching receipt for /Applications/MyAppName.app - Error Domain=com.apple.commerce.client Code=500 "(null)" storelegacy StoreLegacy: Failed to perform in-line receipt renewal for application at path /Applications/MyAppName.app : 'The operation couldn’t be completed. (com.apple.commerce.client error 500.)' (This particular log text is from Mojave; Catalina doesn’t provide many more details) I’m able to reproduce this issue on 3 different Macs (iMac Pro, MacBook Pro 2014, and iMac 2010), 3 different OS’s (Catalina, Mojave, High Sierra), and 4 different Sandbox accounts, one of which is brand new. I’ve made sure my Apple ID is logged out of the Mac App Store, iTunes, and iCloud. I’ve rebooted my Macs countless times. I’ve even gone so far as to install a “clean” version of Catalina on one of my Macs. Nothing seems to help. I contacted Developer Support about this. Unfortunately they didn’t have any answers and suggested I post in the Forums or file a Tech Support request. So I figured I’d try the Forums first to see if anyone had any thoughts. Thanks!