I've paid $99/year every year since 2008. Given inflation, the developer program is cheaper every year (so far any way).

@KayleeSC I've been having the same issue for over a year, at least. Just today I got a reply to one of my bug reports. This time, instead of just clicking on the "Add More Information" button at the end of the report, I clicked on the "Reply to Apple Feedback" link at the bottom of the reply from Apple. After submitting the requested information, in this case confirming that the issue is now resolved, the report still had the purple dot next to it. But as soon as I closed the report (which was appropriate in this case), the purple dot disappeared and the feedback moved from the "Requests" folder back to my "Submitted" folder. So yes, this is a bug in Feedback Assistant. You really should file a bug report on this.

@Etresoft The goal is to use older Asset Catalog based app icons for pre-26, and new Icon Composer based app icons for 26+. With Xcode 26.0, you could make it work using the --enable-icon-stack-fallback-generation=disabled setting. But as of Xcode 26.1, that setting is now being ignored and when the app is run, the Icon Composer based app icon is used for all versions, pre and post 26. While this thread is about macOS, it equally applies to iOS apps. I'm sticking with Xcode 26.0 because I want my old app icons for iOS 18 and older. Xcode 26.1 is now preventing this from being possible.

Are your issues specific to Xcode 26.2? All of my existing behaviors works just fine with Xcode 26.0 and 26.1.1. I also had no trouble creating new custom behaviors and changing their names. I also had no issue deleting those custom behaviors. Though one note about editing a custom behavior's name. After entering the new name, you need to press the return key before clicking the Done button or the new name won't take. Perhaps that is the issue you are seeing. But I have not tested with Xcode 26.2.

@DTS Engineer I really appreciate the response. Very helpful. After looking into SMAppService, it does seem like a launch agent is most appropriate. The biggest issue I have now is trying to figure out how to make this work. My app and its needs are very far from simple. I have a very large data model that is stored locally in a SQLite database and the user can optionally choose to sync their data via iCloud (CloudKit). Trying to figure out how refactor all of the existing code and logic that deals with CKSyncEngine syncing, reading and writing the SQLite database, and updating the in-memory data model into the launch agent, all in a way that can be coordinated with the main GUI app (when it might happen to be running), it going to be, shall I say, challenging. Oh, and doing this in such a way that doesn't change how the iOS version currently works using background tasks.

You do not need to plug your iPhone in to use it with Xcode. Debugging will likely be slower, but Xcode can communicate with your iOS device wirelessly.

Thanks Quinn. Good information.

A standard UITableViewCell with a style of .value1 should give the desired results. If you want your own custom cell class with your own labels, you will need to apply one of two different sets of constraints depending on the current size category. Update the constraints any time the size category changes.

Keep in mind that the user can change the text size category (in the Settings app) while using your app. So your code should be listening for that change and updating the constraints as needed.