Attempting to build and run apps that require a receipt is consistently failing as no masreceipt is stored in the app bundle after the login/password dialog has been submitted. The log typically contains lines starting: StoreLegacy: Failed to renew receipt for application at path... sometimes we get the "app is damaged download again" dialog when attempting to launch We have tried: macOS 10.13.6, Xcode 10.1 macOS 10.15.6, Xcode 11.6 logging out from the App Store creating a new sandbox account (including in a different region) two different projects checked apps are signed with valid certs rebooting, rebuilding, cleaning project of course It's worked plenty of time before but we haven't run such tests for months. Any ideas what we're doing wrong or what we should kick next? TIA

macOS Version: 12.0.1 (21A559) We have an app which auto saves window positions and re-opens and restores them on launch. We normally use `setFrameUsingName:force: to reposition the window. Now in Monterey this works incorrectly if the window is not on the main screen in a multi-screen setup – Monterey relocates the window to the main screen. The position is roughly equivalent to where it was previously on its original screen, i.e. if it was in a corner it moves to roughly the corner on the main screen even if the screen sizes are different. This suggests to us it likely intentional and not a bug per se, but that is just a guess. We've tried using setFrameFromString: after reading the saved user defaults value ourselves, still gets relocated. However reading the user defaults directly, deleting it so AppKit doesn't use it behind the scenes, parsing the frame value from it, and using setFrame:display: restores the correct behaviour. It's a hack, gated by a test for Monterey, but it works. Given it looks like it might be intentional behaviour is there a way to turn it off? Or is there some other fix? TIA

We have an app that uses NetFSMountURLSync and testing under Sonoma beta 4 all calls fail with EPERM (1). Is there a new entitlement required for Sonoma? Something else?

There are multiple reports of Xcode 15.x crashing when performing a verification check on an archive, which makes submitting to the MAS rather a challenge! The earliest report for this year that we've found is a Jan report added to thread 45085 which itself dates from 2016 – an old bug returned maybe? Threads from this year include 749815, 750320 & 758103. Now we've been hit by it: Xcode 15.2 on Ventura -> Boom, Xcode 15.4 on a clean Sonoma -> Boom. We submitted one crash report using the standard “Send to Apple”, have more should DTS request them. When will Apple publish a fix here, or do we need to raise a DTS issue directly?