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...

Yep, and the "App Store Connect Engineer" assumes it's just a normal post...

Dude, try it for yourself! Add a privacy manifest file as I've suggested. Add the right keys and values for your project your code, not the SDKs), and build it.

Obviously I did that at almost midnight, so the ternary operators on lines 4 & 9 are not required, neither is the .disabled modifier on line 3 :)

This reply disappeared, then reappeared, and the two code blocks have been munged together, with the text that I'd put in-between placed above them. Forum bugs ahoy!

If the user clicked it, they clearly received it. Besides, can't you just assume that a notification is actually sent? We assume lots of things, why would you need to confirm this specific thing?

I did originally suggest this approach, then changed my mind as it seems like overkill for this task :)

Yeah, I figured that out a while ago. Forgot I'd still got this outstanding.