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.

The Disney+ app shows an example of it not being just screenshots. The OP could add a couple of extra screenshots in a similar fashion.

Good stuff. iOS development equivalent of "have you tried turning it off and on again?" 😆

Glad it helped. Sorry that I pasted the wrong first bit of the code... Should've been: if("2022/11/27" < "2022/11/28") { Text("'2022/11/27' < '2022/11/28 = correct'") } else { Text("'2022/11/27' >= '2022/11/28' = incorrect") }

Always tip your server... Don't forget to mark an answer as accepted ;)

No. It's written to a plain text file. If you seriously don't want the timestamps you'll have to use your own Logger (the struct that was overriding the os version, with the #if debug in the right place), but you'll lose any of the niceties of os:Logger.

I think this is related to changes made to constraint constants in Interface Builder. Have a look at that, @Claude31.

Doesn't matter. Apple does not provide a means to track things other than inside an app. Once a user exits your app it has only a few seconds before it is completely killed, so it would never be able to do anything in the background regardless of whether someone has agreed to your Ts&Cs.

Because it's in the Developer Programme. When you're enrolled in the programme you see the updates that are available in the programme. If you're currently on 13.0 and there's a 13.1 beta available that's what you'll be shown. The fact you're on 13.0 and there's an update to 13.0.1 is neither here nor there because 13.0.1 isn't in the Developer Programme.