Do you understand how pointless your suggestion is? You haven't offered the name of a session to watch. I already have widgets working; my issue was specifically mentioned in my question. Regardless, I have recently fixed this with help from an ex Apple employee on Mastodon, and no WWDC session would've helped.

If you wouldn't mind, mark my answer as the accepted answer and it'll let others know that your question has a solution :)

Then you may need to generate some sort of unique userId. When the app is launched for the first time and the user doesn't login, generate the id and send that with your request to the server, and reject requests after a number have been made. If the user instead logs in, retrieve the id from your own server and store it in the app. Again, it won't stop deletion and re-installation of the app as a new id will be generated each time.

No, it's putting the fix in the middle of foo, i.e. foStinrg(describing: o.value). Looks like an Xcode bug to me.

Please take note of what I said about using constants and the Notification.Name extension. You should create a name for each notification and use the syntax I provided. This will reduce typos.

17.5 isn't out yet, so I'd say this is the right place as it's the beta they're talking about.

When the brand changes you HAVE to set the modelindex to 0, or it will be left at the previous value, which is what's causing your problem.

No, you didn't. Put the onChange modifier on the SECOND picker as well.

it really is infuriating sometimes. For example, the new ColorPicker. It's a View so it has to be displayed as a View, and it adds its own little palette picker so you can't just say, "Show a ColorPicker when the user presses this other Text button I've created". You always see the palette button, so if you want to have a few of them on different part s of your app, you get that stupid palette everywhere. I just want to show a ColorPicker when the user taps some other button of my design.

No problem. Was fun to do! When working with Bools I try to always name them as though they are positive (so I would've used showTeco rather than hideTeco) unless the switch itself needs to be a negative ("Hide TECO"). The idea is not to confuse myself. I agree on the else [] bit. I didn't know if you wanted them all showing or not, but the change was simple.

Your posts are absolute trash, and do not belong on the Developer Forums. If you want to build your company, posting nonsense on these forums isn't the way to do it. You must realise that. And if you don't, well then I'm going to keep reporting them as spam and Apple will hopefully ban you.

Word salad.

Mark it as resolved so others can see there's a fix for it.

Which betas are you on? "iOS 17.0" is the OS version, not the beta version. What have you tried? Restarting the Mac and the iPad? Checking in the Console app when you plug it in? Reinstalled Xcode? We cannot help you with the tiny amount of information you've given us.

If you've already reported it to the App Store team then why are you reporting it here? This is what I mean by spamming these forums. I don't stand beside spammers, thanks, but I also don't know why you think any app creator on here is going to be able to help you with this? What do you want from us? Agreement that there's an issue in the App Store? Great! I agree, but I can't do anything about it, neither can any of the other app creators on here. Speak to the App Store team again.