Glad you've fixed it. I always find it easier to log stuff out to see whether I'm missing some other state. With regards to debugging and logging: 1. Make sure you pair a watchOS Simulator with an iOS Simulator in the "Devices and Simulators" window. 2. Run your iOS target on the iOS Simulator. 3. Run your watchOS target on the watchOS Simulator that's paired to that iOS Simulator. 4. The output should be displayed in the console window as usual.

The Apple Support Community will bounce it back here because it's about the iPadOS 26 beta.

Claude doesn't have to direct you anywhere other than not here. These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. We don't advertise apps on here; that's not what these forums are for. Go to any Mac/iPhone app related forums.

You can raise a bug at https://feedbackassistant.apple.com/

Yeah, it's a different form of .sheet, as the DTS Engineer noted on line 23 of their fix: .sheet(item: $selectedTransaction) { transaction in. But I was right :) You do need to send the variable in.

You might want to update your feedback report to include that it seems like this was blocked because it's for c u e, which is rude when read out loud.

Yeah, even if it's just there during the beta period for a new major release, i.e. iOS 27, 27, 28 not 26.0.1 etc.

Honestly wondering if it's because this was in a for loop, i.e. for c u e (read it out loud).

The point of my response was that if you use the Simulator you can see the plist file where the defaults are saved, and you can determine whether you were actually writing them (so the issue is in reading them), or if they weren't in the file the issue is in the writing. You're saving a string 1 for a boolean pushIsYes. You should write and read it as a boolean with boolForKey. This can stop you accidentally mixing up values.

They likely suggested you go to the product support forums, not the developer forums.

You don't need to keep adding comments. You have a one-hour window in which to edit your post.

You beat me by 9 seconds 😄

Add your solution as a reply (not a comment), then mark it as the answer, and others will know this worked for you so it might help them. Answered posts are helpful for others because they know there was a solution to the issue.

Quinn, that "a thread" url you added is for this thread...

It's dumb. I could be mean and say it was written by Apple Intelligence...