“build disappears”

Sorry for the noise. I had forgotten to add '.plist' to the id when running launchctl unload. All fixed now. The root process is started from AuthorizationExecuteWithPrivileges and then a setuid(0) before running launchctl. I know that's frowned upon but hopefully by the time the deprecated call disappears any affected users will have already updated :)

You are right that there is no way to share a ClodKit database. An owner can only share a custom record zone in their private database. The default record zone doesn’t support sharing, mentioned here. To share the whole content of a cloudkit database, the following may be worth considering : When an owner shares a custom record zone, all the data in the record zone is shared, and so you an share your dataset by putting the dataset into the zone. All your app users have access to the public database of your CloudKit container, and you can build your own user management system to control the access. Based on this, you might be able to share your data by using the public database instead. To get more information about CloudKit sharing, you might go through this sample code. Best, —— Ziqiao Chen  Worldwide Developer Relations.

Publish like uploading on the app store, or do you mean build

I hadn’t filed a bug report yet because I had assumed it was something I was doing wrong, given that using replaceItem and a temporary folder is presumably a common pattern. I’ll file a report tomorrow - I’m following the iCloud Drive profile instructions you linked to and am now waiting the 24 hours they say I need to wait before I can get the sysdiagnose. Once I have that, I’ll file the report along with a sample project. Perfect, thank you. ...using replaceItem and a temporary folder is presumably a common pattern I didn't get into it above, but there very likely are some nuances/details involved that are a contributing factor. For example, I suspect this doesn't happen if you start with a security-scoped bookmark, which you resolve to a bookmark before each save. I think NSDocument's default implementation also writes out a new file before each save, which means it's always starting with a new URL. That doesn't mean there's anything wrong with what you're doing, but that's probably why this isn't more wid

Thanks. Using AnimationResource.generate(with:) rather than AnimationResource.makeActionAnimation(for:duration:bindTarget:) solves the issue (and setting a material makes sure that the sphere actually fades out and doesn't just disappear at the end). I don't understand the difference though, the two lines of code seem almost identical to me.

I'd like to start with pointing you the following pure SwiftUI TextEditor sample, which may be good enough if your intent is to highlight a range of text (and do basic text editing) in a SwiftUI app: Building rich SwiftUI text experiences. If you do need TextKit 2 for other reasons, I'd suggest that you provide a minimal project that demonstrates the issue for folks to take a closer look. Best, —— Ziqiao Chen  Worldwide Developer Relations.

Hi there @VulcanCCIT , thanks for sharing your timeline. Honestly, you should celebrate that 36-hour turnaround for your iOS build! That is incredibly fast and exactly how the process should work. Unfortunately, my massive delay is specifically for an iOS build, and as of today, I am officially starting my fourth week of waiting. What makes this even more frustrating is that this isn't a new app submission. I have successfully submitted and released over 25 versions of this exact app in the past. Historically, my absolute longest wait was 6 days during the New Year holidays, but it normally takes just 1-2 days. To suddenly hit a 3+ week wall is clearly abnormal. What's worse is Apple's complete silence — ignoring all my tickets, expedited requests, and calls. It is absolutely irresponsible on their end to leave developers completely in the dark for nearly a month with zero communication. I hope your Mac version gets sorted out soon, but definitely consider yourself very lucky on the iOS side

First up, I want to make sure you’re aware of this: Apple Security Research Device Program But as to your specific situation, you could work with your customers to get builds of their app that are more amenable to your testing. For example, a development-signed build, with the get-task-allow entitlement, will allow you to attach with the debugger. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I have a second app which is already live on the App Store. I pushed an update to this app, and it was approved and is Pending Developer Release. I generated a promo code, and redeemed it. It worked fine. So, maybe the Pending Developer Release -> Promo Code method for giving media access to your prerelease 1.0 builds no longer works. Apple: Please document this!