You beat me by 9 seconds 😄

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

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

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.

Honestly wondering if it's because this was in a for loop, i.e. for c u e (read it 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.

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, 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 can raise a bug at https://feedbackassistant.apple.com/

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.

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

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.

@Tinn_Vision That's the sort of information you should put in the original post so people don't have to ask you for it. You put a giant red X to show that it doesn't work on visionOS, but then didn't say_ why i_t doesn't work.

Doesn't sound like you understand that these forums aren't here for advertising. And they aren't here for insults either.

iOS 26.1 has been released, so please check that the issue is no longer present in the released version. If it is, please raise a feedback report at: https://feedbackassistant.apple.com/ then post the FB number here. Secondly, don't hijack someone else's thread. Your issue is unrelated to the original post, and you should create your own thread instead.